Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a4e805bb343d14bc16ef48969b78a5076b60a799aeefe7684b855494664b492

Tx prefix hash: 8e900306f5966f8cdc7370d17f812b3edd9c2948f66fd134dde68e57858deaa4
Tx public key: 236f6b9665a5440e60697c2c153b7d440d830a7c28116df4db9f73cd1a22b98f
Timestamp: 1712431392 Timestamp [UCT]: 2024-04-06 19:23:12 Age [y:d:h:m:s]: 01:057:19:47:16
Block: 994773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302363 RingCT/type: yes/0
Extra: 01236f6b9665a5440e60697c2c153b7d440d830a7c28116df4db9f73cd1a22b98f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 644e21e24b8a36c52943f8f6c9a0493da33f6abeb65ffda2d684142024da2df5 0.600000000000 1455177 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": 994783, "vin": [ { "gen": { "height": 994773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "644e21e24b8a36c52943f8f6c9a0493da33f6abeb65ffda2d684142024da2df5" } } ], "extra": [ 1, 35, 111, 107, 150, 101, 165, 68, 14, 96, 105, 124, 44, 21, 59, 125, 68, 13, 131, 10, 124, 40, 17, 109, 244, 219, 159, 115, 205, 26, 34, 185, 143, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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