Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4267f77444f7b73120b27f3041b430bbb1971de127adc04938df290bfacddb09

Tx prefix hash: 2c44a69e7e4a9a652c6fed01ba7592bed45254230215b322309b57f97c66b2c4
Tx public key: e22e36a0e36743f7c8f21db0b2f3e355de60698f7620a93db697bc71cbfc961b
Timestamp: 1632219167 Timestamp [UCT]: 2021-09-21 10:12:47 Age [y:d:h:m:s]: 04:044:05:07:19
Block: 338123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1066026 RingCT/type: yes/0
Extra: 01e22e36a0e36743f7c8f21db0b2f3e355de60698f7620a93db697bc71cbfc961b021100000001a272b9cb000000000000000000

1 output(s) for total of 46.522021146000 dcy

stealth address amount amount idx
00: 3a83de94bb9e8e1a43ce3902c356f0940f6fe6ad5050b8824a8e3664de733bdf 46.522021146000 695990 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 338133, "vin": [ { "gen": { "height": 338123 } } ], "vout": [ { "amount": 46522021146, "target": { "key": "3a83de94bb9e8e1a43ce3902c356f0940f6fe6ad5050b8824a8e3664de733bdf" } } ], "extra": [ 1, 226, 46, 54, 160, 227, 103, 67, 247, 200, 242, 29, 176, 178, 243, 227, 85, 222, 96, 105, 143, 118, 32, 169, 61, 182, 151, 188, 113, 203, 252, 150, 27, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8