Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e72ccdfb5f374abdf1f6d2777479e675fb288add81991391511468cf62c56773

Tx prefix hash: fc56026913915e92dd1056d7e6f39803dce8e258b11293568fcf83b0a1b042b2
Tx public key: 25fb5bcb58b640f99a3194d1a301f9b7efb065a87f16d10d58f2655c05a883f2
Timestamp: 1703922255 Timestamp [UCT]: 2023-12-30 07:44:15 Age [y:d:h:m:s]: 01:326:14:42:29
Block: 924256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492274 RingCT/type: yes/0
Extra: 0125fb5bcb58b640f99a3194d1a301f9b7efb065a87f16d10d58f2655c05a883f20211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 323ac865f2d802c1bcf2929466dd8a063f95d6b980bf5838182ac8546df32b66 0.600000000000 1382000 of 15

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": 924266, "vin": [ { "gen": { "height": 924256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "323ac865f2d802c1bcf2929466dd8a063f95d6b980bf5838182ac8546df32b66" } } ], "extra": [ 1, 37, 251, 91, 203, 88, 182, 64, 249, 154, 49, 148, 209, 163, 1, 249, 183, 239, 176, 101, 168, 127, 22, 209, 13, 88, 242, 101, 92, 5, 168, 131, 242, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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