Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcdd0da6913a18a183dc3cc4ba377bc2179a4134ca496fe3a1096bef6c181e13

Tx prefix hash: fddfbf8e261fe1fe340de50600164d01cc48a4cbc11e41b288bbb4f5b8afa6a0
Tx public key: 150cb43226ddfa3d68f5bb0a1609bd4d8e9e25895f844bfc83e72922410ca694
Timestamp: 1577047447 Timestamp [UCT]: 2019-12-22 20:44:07 Age [y:d:h:m:s]: 05:142:06:52:36
Block: 29740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1251300 RingCT/type: yes/0
Extra: 01150cb43226ddfa3d68f5bb0a1609bd4d8e9e25895f844bfc83e72922410ca69402110000001d4ac5aa02000000000000000000

1 output(s) for total of 489.170092809000 dcy

stealth address amount amount idx
00: 161e09b19f59d0ccbf240bab9f506c4064c3130d68776be9f421e6c5b52feb99 489.170092809000 48984 of 0

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": 29750, "vin": [ { "gen": { "height": 29740 } } ], "vout": [ { "amount": 489170092809, "target": { "key": "161e09b19f59d0ccbf240bab9f506c4064c3130d68776be9f421e6c5b52feb99" } } ], "extra": [ 1, 21, 12, 180, 50, 38, 221, 250, 61, 104, 245, 187, 10, 22, 9, 189, 77, 142, 158, 37, 137, 95, 132, 75, 252, 131, 231, 41, 34, 65, 12, 166, 148, 2, 17, 0, 0, 0, 29, 74, 197, 170, 2, 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