Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c27f688ac78c5fd0e4c76148869088fbb77cd7680ffed0957b6db922804b847

Tx prefix hash: 3fe4e54defedb6211f075510f0312d11346186a0250a73e15f0eaa09dc8e77dc
Tx public key: aa9ae25ecb864d2c07c8e89412ee43731f56ea93726bfb2fce74e5f40241bc28
Timestamp: 1751399344 Timestamp [UCT]: 2025-07-01 19:49:04 Age [y:d:h:m:s]: 00:214:17:00:17
Block: 1316747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151587 RingCT/type: yes/0
Extra: 01aa9ae25ecb864d2c07c8e89412ee43731f56ea93726bfb2fce74e5f40241bc28021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02cdaf9264a9fc1360f30826efdf2febeaa5920d01590e1f180c51f06dc0a750 0.600000000000 1804410 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": 1316757, "vin": [ { "gen": { "height": 1316747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02cdaf9264a9fc1360f30826efdf2febeaa5920d01590e1f180c51f06dc0a750" } } ], "extra": [ 1, 170, 154, 226, 94, 203, 134, 77, 44, 7, 200, 232, 148, 18, 238, 67, 115, 31, 86, 234, 147, 114, 107, 251, 47, 206, 116, 229, 244, 2, 65, 188, 40, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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