Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b40cd8bac3aacd671f2a0b16002b132f2324027d2a9939adbbedb18dfceb399

Tx prefix hash: 04833ec647a40c0b7b15e31ba3c5d36f88cf01a9daefa26fa346e9b150e8eb78
Tx public key: 97975dee956ec5ef15b0b540be7734c8bd64d5ab2a74e28df4d52260e3ab56fe
Timestamp: 1703742845 Timestamp [UCT]: 2023-12-28 05:54:05 Age [y:d:h:m:s]: 01:171:03:45:20
Block: 922775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383373 RingCT/type: yes/0
Extra: 0197975dee956ec5ef15b0b540be7734c8bd64d5ab2a74e28df4d52260e3ab56fe02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b3f3ed178db299743a767f3b55e4d6646a435414e8e14915ca2ff3d28338c82 0.600000000000 1380479 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": 922785, "vin": [ { "gen": { "height": 922775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b3f3ed178db299743a767f3b55e4d6646a435414e8e14915ca2ff3d28338c82" } } ], "extra": [ 1, 151, 151, 93, 238, 149, 110, 197, 239, 21, 176, 181, 64, 190, 119, 52, 200, 189, 100, 213, 171, 42, 116, 226, 141, 244, 213, 34, 96, 227, 171, 86, 254, 2, 17, 0, 0, 0, 1, 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