Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1efe09036261ff909bf6540bcec28d7243797fb354495b01c245fb86f8a2d46f

Tx prefix hash: edd8c3cdf6e784d02ca8b8e3ad8480a4094d7d371451e6281776c2a48f87a36c
Tx public key: fe0498bf3e84b2022d4944c3e1601e3c40883e64b3562aed991844342bce9b7e
Timestamp: 1721849304 Timestamp [UCT]: 2024-07-24 19:28:24 Age [y:d:h:m:s]: 00:308:20:01:54
Block: 1072877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220690 RingCT/type: yes/0
Extra: 01fe0498bf3e84b2022d4944c3e1601e3c40883e64b3562aed991844342bce9b7e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e045e8ab8901433be55aecabf3a9a5a630029a6829c263649ee743b3e5d4d873 0.600000000000 1545374 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": 1072887, "vin": [ { "gen": { "height": 1072877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e045e8ab8901433be55aecabf3a9a5a630029a6829c263649ee743b3e5d4d873" } } ], "extra": [ 1, 254, 4, 152, 191, 62, 132, 178, 2, 45, 73, 68, 195, 225, 96, 30, 60, 64, 136, 62, 100, 179, 86, 42, 237, 153, 24, 68, 52, 43, 206, 155, 126, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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