Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34a385f416c1ba8805ffc42c6bbf3fc0aae5f8388d5f0b0af084d6e8aad00dea

Tx prefix hash: f36f25f10c96f4d5810e0678dfe28589c02d67e5657134122a0a1726abf7d6f7
Tx public key: f1e17e22c75439597298cf472fcc26e3cfa51b0cc9e81a3d2c8281a2398a6618
Timestamp: 1729476827 Timestamp [UCT]: 2024-10-21 02:13:47 Age [y:d:h:m:s]: 00:034:01:09:02
Block: 1136081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24336 RingCT/type: yes/0
Extra: 01f1e17e22c75439597298cf472fcc26e3cfa51b0cc9e81a3d2c8281a2398a6618021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e6203a4b06e5daa2ac54b3eb6b9623ea58150dc1995cdcad76989fec55a4898 0.600000000000 1619424 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": 1136091, "vin": [ { "gen": { "height": 1136081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e6203a4b06e5daa2ac54b3eb6b9623ea58150dc1995cdcad76989fec55a4898" } } ], "extra": [ 1, 241, 225, 126, 34, 199, 84, 57, 89, 114, 152, 207, 71, 47, 204, 38, 227, 207, 165, 27, 12, 201, 232, 26, 61, 44, 130, 129, 162, 57, 138, 102, 24, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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