Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 251cefc29e2b9c61019ce143cec6498c07e8d65b1807b1b01f1eebc3f509902d

Tx prefix hash: 1a0ce5175667eabf19e60dbe118b5d708a47682a74c7acb7bfd61d7d40909bb1
Tx public key: 48daf9189c0fbbadb94c7ce424a253c5886cb45fac7bec5e6b3be56f24fb60f1
Timestamp: 1755738588 Timestamp [UCT]: 2025-08-21 01:09:48 Age [y:d:h:m:s]: 00:137:22:46:15
Block: 1350955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98584 RingCT/type: yes/0
Extra: 0148daf9189c0fbbadb94c7ce424a253c5886cb45fac7bec5e6b3be56f24fb60f10211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05f2a3a5f764955335959a1f5182043530f52f0dc38d28c95ce70cee538f95f7 0.600000000000 1838902 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": 1350965, "vin": [ { "gen": { "height": 1350955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05f2a3a5f764955335959a1f5182043530f52f0dc38d28c95ce70cee538f95f7" } } ], "extra": [ 1, 72, 218, 249, 24, 156, 15, 187, 173, 185, 76, 124, 228, 36, 162, 83, 197, 136, 108, 180, 95, 172, 123, 236, 94, 107, 59, 229, 111, 36, 251, 96, 241, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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