Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66b47c1380a0eec0cc76b3eff95d69f1e596440470268fb65ff8661f7982702b

Tx prefix hash: e1f35139188bb7424fe27b5130de96e759ee51a1c74c3d97e0f8bf3745a74ebe
Tx public key: cba5bc0e865c8d51ce66b8d277b98fe90c65c4e07cd916f2f9f3c57f32a3ccf4
Timestamp: 1635952958 Timestamp [UCT]: 2021-11-03 15:22:38 Age [y:d:h:m:s]: 03:199:07:34:05
Block: 366548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 920803 RingCT/type: yes/0
Extra: 01cba5bc0e865c8d51ce66b8d277b98fe90c65c4e07cd916f2f9f3c57f32a3ccf402110000000a42b3953e000000000000000000

1 output(s) for total of 37.451974071000 dcy

stealth address amount amount idx
00: d52ff77a17feb1a6c88c17ec1a70c1bfbeebfd78dde67b404f39ad964f5edcae 37.451974071000 744032 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": 366558, "vin": [ { "gen": { "height": 366548 } } ], "vout": [ { "amount": 37451974071, "target": { "key": "d52ff77a17feb1a6c88c17ec1a70c1bfbeebfd78dde67b404f39ad964f5edcae" } } ], "extra": [ 1, 203, 165, 188, 14, 134, 92, 141, 81, 206, 102, 184, 210, 119, 185, 143, 233, 12, 101, 196, 224, 124, 217, 22, 242, 249, 243, 197, 127, 50, 163, 204, 244, 2, 17, 0, 0, 0, 10, 66, 179, 149, 62, 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