Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 894ebc9e32bf1d02c0750a1393a0e65a6d3ccc63eb472951bb006b793f38b07c

Tx prefix hash: 069a4e161615185802b31c3581d5bc2dc083871a526021d40c44b179e3a059a7
Tx public key: c409ddab1feaf90052b1ad620bbf97bdbd10c937037b5cc33d689ff8306dc305
Timestamp: 1748301927 Timestamp [UCT]: 2025-05-26 23:25:27 Age [y:d:h:m:s]: 00:248:04:51:06
Block: 1291659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174990 RingCT/type: yes/0
Extra: 01c409ddab1feaf90052b1ad620bbf97bdbd10c937037b5cc33d689ff8306dc30502110000000186ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d994b0e9ff2e34a82177ee94d9c6659249a47f6fb7f4fcc73fb27ac6c3d790f 0.600000000000 1779130 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": 1291669, "vin": [ { "gen": { "height": 1291659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d994b0e9ff2e34a82177ee94d9c6659249a47f6fb7f4fcc73fb27ac6c3d790f" } } ], "extra": [ 1, 196, 9, 221, 171, 31, 234, 249, 0, 82, 177, 173, 98, 11, 191, 151, 189, 189, 16, 201, 55, 3, 123, 92, 195, 61, 104, 159, 248, 48, 109, 195, 5, 2, 17, 0, 0, 0, 1, 134, 174, 47, 13, 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