Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15f22fc60de3c422b013fec6c1244140607a544181d49aa4a8abbf1cbc9f4b2e

Tx prefix hash: 56c894d6eb940ee81afecfefe6f1a340412ebda1e13a74eb4ef133820d793693
Tx public key: 6c53defad829ae21aadd920156237cc8768e0b6c3f81d0137a1bbaf70b4e08b1
Timestamp: 1765286282 Timestamp [UCT]: 2025-12-09 13:18:02 Age [y:d:h:m:s]: 00:031:04:05:44
Block: 1429860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22332 RingCT/type: yes/0
Extra: 016c53defad829ae21aadd920156237cc8768e0b6c3f81d0137a1bbaf70b4e08b1021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b55a57ce726e0e97bb725c70859a8501409dad3d6db714018fb035259ee9dd4a 0.600000000000 1918593 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": 1429870, "vin": [ { "gen": { "height": 1429860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b55a57ce726e0e97bb725c70859a8501409dad3d6db714018fb035259ee9dd4a" } } ], "extra": [ 1, 108, 83, 222, 250, 216, 41, 174, 33, 170, 221, 146, 1, 86, 35, 124, 200, 118, 142, 11, 108, 63, 129, 208, 19, 122, 27, 186, 247, 11, 78, 8, 177, 2, 17, 0, 0, 0, 1, 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