Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb1410ea5bc7267bc6d999632db6c7f35219854ca63d1241ce21d4b5033e6440

Tx prefix hash: 66d9b9f0a797471398d3fef1e41d42ab62f0377cade9ff40f1d6fdab09d9ea8d
Tx public key: 7bb92760b1edc7eac0ed73478aacc9fd3a173c54df7a6103c656d634f6a4eade
Timestamp: 1748979392 Timestamp [UCT]: 2025-06-03 19:36:32 Age [y:d:h:m:s]: 00:240:09:48:41
Block: 1297270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169416 RingCT/type: yes/0
Extra: 017bb92760b1edc7eac0ed73478aacc9fd3a173c54df7a6103c656d634f6a4eade02110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e9ed973cfb64cc56ce19480d79f9fe5cb60f5d97472a788e679b013ccbd0a62 0.600000000000 1784787 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": 1297280, "vin": [ { "gen": { "height": 1297270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e9ed973cfb64cc56ce19480d79f9fe5cb60f5d97472a788e679b013ccbd0a62" } } ], "extra": [ 1, 123, 185, 39, 96, 177, 237, 199, 234, 192, 237, 115, 71, 138, 172, 201, 253, 58, 23, 60, 84, 223, 122, 97, 3, 198, 86, 214, 52, 246, 164, 234, 222, 2, 17, 0, 0, 0, 5, 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