Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 458464e54676659e9e1da4c12cc3a7776390591a3a0b688bd272462ee355d8f2

Tx prefix hash: 819d2854ecb0f47fb1737f2029bdb556270e6a255ce5ecab6bd0a35cc6db731f
Tx public key: ddc16a2f473403b54b33c57e8d2252b29c29bde79ed826f0711eeeeeb096e761
Timestamp: 1579011922 Timestamp [UCT]: 2020-01-14 14:25:22 Age [y:d:h:m:s]: 05:050:23:00:14
Block: 45338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186648 RingCT/type: yes/0
Extra: 01ddc16a2f473403b54b33c57e8d2252b29c29bde79ed826f0711eeeeeb096e7610211000000078a2ee0d9000000000000000000

1 output(s) for total of 434.302045774000 dcy

stealth address amount amount idx
00: b4c37dd2f873673908603e626cb5f01ae08c5febd48719e2be30504b5014e5ab 434.302045774000 82806 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": 45348, "vin": [ { "gen": { "height": 45338 } } ], "vout": [ { "amount": 434302045774, "target": { "key": "b4c37dd2f873673908603e626cb5f01ae08c5febd48719e2be30504b5014e5ab" } } ], "extra": [ 1, 221, 193, 106, 47, 71, 52, 3, 181, 75, 51, 197, 126, 141, 34, 82, 178, 156, 41, 189, 231, 158, 216, 38, 240, 113, 30, 238, 238, 176, 150, 231, 97, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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