Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc6a8c53466c2766794962aaa38bf5dbd8b4bd9ba4d5da27d4ccf77f6783dc62

Tx prefix hash: 6bbe4dd411a308e86afc4c1d0dcf7d01660c3eddc3a9dbe0869af17f29101aec
Tx public key: e78eba382154f7beca5bf7e4d003a26a85bc51a585a6406c0596cbefdaa8d0e1
Timestamp: 1763802460 Timestamp [UCT]: 2025-11-22 09:07:40 Age [y:d:h:m:s]: 00:004:05:43:31
Block: 1417558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3046 RingCT/type: yes/0
Extra: 01e78eba382154f7beca5bf7e4d003a26a85bc51a585a6406c0596cbefdaa8d0e1021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9d03996b4cfbba72de1548731eaf09df6d19cea81fc34ec3ce05d1646eb4ebe 0.600000000000 1906083 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": 1417568, "vin": [ { "gen": { "height": 1417558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9d03996b4cfbba72de1548731eaf09df6d19cea81fc34ec3ce05d1646eb4ebe" } } ], "extra": [ 1, 231, 142, 186, 56, 33, 84, 247, 190, 202, 91, 247, 228, 208, 3, 162, 106, 133, 188, 81, 165, 133, 166, 64, 108, 5, 150, 203, 239, 218, 168, 208, 225, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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