Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fdc8447e1432f5c23950fb3f103e0ac403695ea43a0f2bc345cf50376189847

Tx prefix hash: 96229609ae726af454e85266e864e249571ab69664a4a82e01207d2f9aaa2dff
Tx public key: d95875db5b0bbf2c3291ead25516dfff7d56673ab7d7249139d9d15ccdc92155
Timestamp: 1736078302 Timestamp [UCT]: 2025-01-05 11:58:22 Age [y:d:h:m:s]: 00:094:00:01:11
Block: 1190728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66962 RingCT/type: yes/0
Extra: 01d95875db5b0bbf2c3291ead25516dfff7d56673ab7d7249139d9d15ccdc9215502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0eb1be63debe74e1eb7b0f8e2520b647c7e55e92a2dd9e1dec02e2acee4c8e9 0.600000000000 1677247 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": 1190738, "vin": [ { "gen": { "height": 1190728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0eb1be63debe74e1eb7b0f8e2520b647c7e55e92a2dd9e1dec02e2acee4c8e9" } } ], "extra": [ 1, 217, 88, 117, 219, 91, 11, 191, 44, 50, 145, 234, 210, 85, 22, 223, 255, 125, 86, 103, 58, 183, 215, 36, 145, 57, 217, 209, 92, 205, 201, 33, 85, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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