Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fa8b716f0cc161217bcf7241fa595bde3d717581723e7b4f133453c50e4dfd2

Tx prefix hash: 63f66021487216631e80c8077ad6fb8e7e11d4336d66ae73dd57c24ac6f98705
Tx public key: ec3f6234c62827d8488a75854298374bc8ee3d120d2bf441599c3dda9934ea46
Timestamp: 1580720012 Timestamp [UCT]: 2020-02-03 08:53:32 Age [y:d:h:m:s]: 04:329:10:58:04
Block: 57842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126672 RingCT/type: yes/0
Extra: 01ec3f6234c62827d8488a75854298374bc8ee3d120d2bf441599c3dda9934ea46021100000001d81c26c0000000000000000000

1 output(s) for total of 394.771929333000 dcy

stealth address amount amount idx
00: c0feeebb8125e050532325fc65cef91dc5dc8acc021027f0f99125b21929eee7 394.771929333000 106934 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": 57852, "vin": [ { "gen": { "height": 57842 } } ], "vout": [ { "amount": 394771929333, "target": { "key": "c0feeebb8125e050532325fc65cef91dc5dc8acc021027f0f99125b21929eee7" } } ], "extra": [ 1, 236, 63, 98, 52, 198, 40, 39, 216, 72, 138, 117, 133, 66, 152, 55, 75, 200, 238, 61, 18, 13, 43, 244, 65, 89, 156, 61, 218, 153, 52, 234, 70, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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