Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2f7ce0b0673ac71613a721e1b11d743a2058cfe80d28ad80b0f0294114bf118

Tx prefix hash: f4a5d9306de679f7fd0834859d1c5d00d9a1a3932261540e0fea44d67fae2141
Tx public key: 22fc0749f9b91dc2e18503834319324da365f97b926941b0fdf741325fef1c1e
Timestamp: 1727830018 Timestamp [UCT]: 2024-10-02 00:46:58 Age [y:d:h:m:s]: 00:113:01:38:41
Block: 1122473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80790 RingCT/type: yes/0
Extra: 0122fc0749f9b91dc2e18503834319324da365f97b926941b0fdf741325fef1c1e021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13e228948e4b598235c84d372baf1d2d2f1f5482c3baf2d445825a1852773c33 0.600000000000 1604918 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": 1122483, "vin": [ { "gen": { "height": 1122473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13e228948e4b598235c84d372baf1d2d2f1f5482c3baf2d445825a1852773c33" } } ], "extra": [ 1, 34, 252, 7, 73, 249, 185, 29, 194, 225, 133, 3, 131, 67, 25, 50, 77, 163, 101, 249, 123, 146, 105, 65, 176, 253, 247, 65, 50, 95, 239, 28, 30, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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