Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77c4a1f15d6f2eeb51880986e30adf135531eedb455ce79ef89b361848db9a8c

Tx prefix hash: 4eeac9716f751e92409d61051dcd69e2863e815bcbed91317492e0cd351df824
Tx public key: 6b8bbfa881f558370f73d86b4d8e8a3ae9a8998b220e4eb9e72ee1709551192d
Timestamp: 1749271823 Timestamp [UCT]: 2025-06-07 04:50:23 Age [y:d:h:m:s]: 00:161:23:43:47
Block: 1299683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113456 RingCT/type: yes/0
Extra: 016b8bbfa881f558370f73d86b4d8e8a3ae9a8998b220e4eb9e72ee1709551192d02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21fb8d0bb78c9df3182bccf8f7a74ad1eaa43372988f5e9985b4be0270933c3a 0.600000000000 1787220 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": 1299693, "vin": [ { "gen": { "height": 1299683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21fb8d0bb78c9df3182bccf8f7a74ad1eaa43372988f5e9985b4be0270933c3a" } } ], "extra": [ 1, 107, 139, 191, 168, 129, 245, 88, 55, 15, 115, 216, 107, 77, 142, 138, 58, 233, 168, 153, 139, 34, 14, 78, 185, 231, 46, 225, 112, 149, 81, 25, 45, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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