Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d570e64209dd692f0cf0a42028542a75fe35ea0d32f4f1b28aee3d82f32d65a5

Tx prefix hash: 0dadd78bd2753707936688de9929b1c690578e06286ecf5e05c69f804f494c8b
Tx public key: 0c1f81fe5701a39398d54c03796c10837945cf77fa8fe5e2ee7610895a6f4bb4
Timestamp: 1750857046 Timestamp [UCT]: 2025-06-25 13:10:46 Age [y:d:h:m:s]: 00:136:18:27:04
Block: 1312535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95683 RingCT/type: yes/0
Extra: 010c1f81fe5701a39398d54c03796c10837945cf77fa8fe5e2ee7610895a6f4bb4021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa6fd1ebdcdc0f4fc4e1a048d27ef2f4057565a7bde8a0fd2bb839a7bd916188 0.600000000000 1800168 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": 1312545, "vin": [ { "gen": { "height": 1312535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa6fd1ebdcdc0f4fc4e1a048d27ef2f4057565a7bde8a0fd2bb839a7bd916188" } } ], "extra": [ 1, 12, 31, 129, 254, 87, 1, 163, 147, 152, 213, 76, 3, 121, 108, 16, 131, 121, 69, 207, 119, 250, 143, 229, 226, 238, 118, 16, 137, 90, 111, 75, 180, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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