Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70ed17c88ff2c88ca9b33dbe639266ab57a5b8f4d489efe1affc96913d88108b

Tx prefix hash: ae36426fa34c76f6208d1615783c8c706b01b714d057916f17268223479569a1
Tx public key: e3df9ddaecac98fc23986d498feee5e1c63c002edcb5e7779027c63a82ab6d7b
Timestamp: 1582035057 Timestamp [UCT]: 2020-02-18 14:10:57 Age [y:d:h:m:s]: 05:110:18:00:06
Block: 67457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1232328 RingCT/type: yes/0
Extra: 01e3df9ddaecac98fc23986d498feee5e1c63c002edcb5e7779027c63a82ab6d7b021100000004c71d3ff9000000000000000000

1 output(s) for total of 366.849358247000 dcy

stealth address amount amount idx
00: 1c1fa5e237a7e35f79e980bd700f57dee79817a71e821485f6554d594c2687e7 366.849358247000 124308 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": 67467, "vin": [ { "gen": { "height": 67457 } } ], "vout": [ { "amount": 366849358247, "target": { "key": "1c1fa5e237a7e35f79e980bd700f57dee79817a71e821485f6554d594c2687e7" } } ], "extra": [ 1, 227, 223, 157, 218, 236, 172, 152, 252, 35, 152, 109, 73, 143, 238, 229, 225, 198, 60, 0, 46, 220, 181, 231, 119, 144, 39, 198, 58, 130, 171, 109, 123, 2, 17, 0, 0, 0, 4, 199, 29, 63, 249, 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