Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30e9b73ce961fc7cb44ff8e9dea088a3c3c00d3f060780db1a29a1bff5c54264

Tx prefix hash: bc01bd3b6f7ab565d08802860be2051e4a359abbec782baeb651f4bf1a0603d5
Tx public key: 0c34fa4505b2833a159165822c922b90b995324e29db7ce089e6bcbf8c59b4eb
Timestamp: 1760529213 Timestamp [UCT]: 2025-10-15 11:53:33 Age [y:d:h:m:s]: 00:108:05:58:59
Block: 1390452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77318 RingCT/type: yes/0
Extra: 010c34fa4505b2833a159165822c922b90b995324e29db7ce089e6bcbf8c59b4eb0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b2f15fd7f4e925e6c1613b5d99423c6728669bb204cc61b72ece6cca502640a 0.600000000000 1878697 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": 1390462, "vin": [ { "gen": { "height": 1390452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b2f15fd7f4e925e6c1613b5d99423c6728669bb204cc61b72ece6cca502640a" } } ], "extra": [ 1, 12, 52, 250, 69, 5, 178, 131, 58, 21, 145, 101, 130, 44, 146, 43, 144, 185, 149, 50, 78, 41, 219, 124, 224, 137, 230, 188, 191, 140, 89, 180, 235, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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