Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c7a158c8783bcd9f473e9a6ee1000fe141396d1f4e58ccc45b4b0d6766b5e9a

Tx prefix hash: bb26fb55d7103bf91334408287918fb6b329dc44abcc33e9e291f4c620a5d6d7
Tx public key: d0b0147ef41ffacbddc2de6277285e7fda6a789123810f306c36183a2fae4da0
Timestamp: 1659478321 Timestamp [UCT]: 2022-08-02 22:12:01 Age [y:d:h:m:s]: 02:106:04:37:07
Block: 557381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597303 RingCT/type: yes/0
Extra: 01d0b0147ef41ffacbddc2de6277285e7fda6a789123810f306c36183a2fae4da0021100000003faf35c9c000000000000000000

1 output(s) for total of 8.733040789000 dcy

stealth address amount amount idx
00: 83fcf24ff44db7bb3a45965f96dcbf7e8aa5d244d3bb0bc3c357e5834dccdf44 8.733040789000 989397 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": 557391, "vin": [ { "gen": { "height": 557381 } } ], "vout": [ { "amount": 8733040789, "target": { "key": "83fcf24ff44db7bb3a45965f96dcbf7e8aa5d244d3bb0bc3c357e5834dccdf44" } } ], "extra": [ 1, 208, 176, 20, 126, 244, 31, 250, 203, 221, 194, 222, 98, 119, 40, 94, 127, 218, 106, 120, 145, 35, 129, 15, 48, 108, 54, 24, 58, 47, 174, 77, 160, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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