Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6216c2027c635521b3ae257dc0f336a991540395d94b866609be48422b2e34c

Tx prefix hash: 1d7f926d0417714af51d507f75a0e9cbd3a2c033d2a4a3bf527f2f12d314b074
Tx public key: 4e0fe8d5d12714a0723f11d066659abffd7764815770dee7f98d8615df6043ca
Timestamp: 1736251380 Timestamp [UCT]: 2025-01-07 12:03:00 Age [y:d:h:m:s]: 00:099:10:39:43
Block: 1192145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70863 RingCT/type: yes/0
Extra: 014e0fe8d5d12714a0723f11d066659abffd7764815770dee7f98d8615df6043ca021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2300f3f37584682b57c75cbdc17489434e2e4cd6b09d535969b031cc1b5e0fa2 0.600000000000 1678692 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": 1192155, "vin": [ { "gen": { "height": 1192145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2300f3f37584682b57c75cbdc17489434e2e4cd6b09d535969b031cc1b5e0fa2" } } ], "extra": [ 1, 78, 15, 232, 213, 209, 39, 20, 160, 114, 63, 17, 208, 102, 101, 154, 191, 253, 119, 100, 129, 87, 112, 222, 231, 249, 141, 134, 21, 223, 96, 67, 202, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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