Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d94189b208953f4c57b72df67f7965a80c417526c1c59dcf20d06a8b05b5979a

Tx prefix hash: 48423c9598b681b65e3c7795e2d04b1296e01ff48d0a008d3c516a52e5003cfe
Tx public key: 5287892f1db8878d8c8c7a7ce70a4a0677a380350ff98e37d54435fad57cddaf
Timestamp: 1736416041 Timestamp [UCT]: 2025-01-09 09:47:21 Age [y:d:h:m:s]: 00:342:05:50:10
Block: 1193507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242159 RingCT/type: yes/0
Extra: 015287892f1db8878d8c8c7a7ce70a4a0677a380350ff98e37d54435fad57cddaf0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bb1eb839acb1ea98e4ac72c8e839e7646526e39af8862365cbee9e6e123e614 0.600000000000 1680068 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": 1193517, "vin": [ { "gen": { "height": 1193507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bb1eb839acb1ea98e4ac72c8e839e7646526e39af8862365cbee9e6e123e614" } } ], "extra": [ 1, 82, 135, 137, 47, 29, 184, 135, 141, 140, 140, 122, 124, 231, 10, 74, 6, 119, 163, 128, 53, 15, 249, 142, 55, 213, 68, 53, 250, 213, 124, 221, 175, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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