Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ee79c0144033fa5e3d6eb9a6191da83a433de09f850ec105c18a194ab47dde1

Tx prefix hash: 40b3a27998272e7e15d87b583b0de6b0784a5bade2a0cd21ef140e3fc6242c64
Tx public key: a903fe837d082e34290f9ab4f822e8a51e8051838ab4d249a00ee7ed2e98c9e6
Timestamp: 1736404495 Timestamp [UCT]: 2025-01-09 06:34:55 Age [y:d:h:m:s]: 00:086:12:41:44
Block: 1193421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61615 RingCT/type: yes/0
Extra: 01a903fe837d082e34290f9ab4f822e8a51e8051838ab4d249a00ee7ed2e98c9e602110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1068473cbd2d695553af91cb9c622472feb9f7f1ce5c6a650610f0442936ce46 0.600000000000 1679982 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": 1193431, "vin": [ { "gen": { "height": 1193421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1068473cbd2d695553af91cb9c622472feb9f7f1ce5c6a650610f0442936ce46" } } ], "extra": [ 1, 169, 3, 254, 131, 125, 8, 46, 52, 41, 15, 154, 180, 248, 34, 232, 165, 30, 128, 81, 131, 138, 180, 210, 73, 160, 14, 231, 237, 46, 152, 201, 230, 2, 17, 0, 0, 0, 13, 31, 10, 83, 235, 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