Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 641df29db3c4d3ff684331f85c05e471c4a20d6b8db9671cadbb4094eb26d187

Tx prefix hash: d37b4e8fb6999d3f69a1e62c4d8b5044648dcd34f382f1d61c1f149a7777473d
Tx public key: e58e0b78f8484b7125c81f4d756a93f3e8c37399b583583dc00d7a140861ec59
Timestamp: 1577181538 Timestamp [UCT]: 2019-12-24 09:58:58 Age [y:d:h:m:s]: 05:160:03:12:15
Block: 30570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1264371 RingCT/type: yes/0
Extra: 01e58e0b78f8484b7125c81f4d756a93f3e8c37399b583583dc00d7a140861ec590211000000054943cd9f000000000000000000

1 output(s) for total of 486.098628623000 dcy

stealth address amount amount idx
00: e70f6f576ee85b771dd0d6dd9736a9168abd82a00103663d9bde3404cf384370 486.098628623000 50478 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": 30580, "vin": [ { "gen": { "height": 30570 } } ], "vout": [ { "amount": 486098628623, "target": { "key": "e70f6f576ee85b771dd0d6dd9736a9168abd82a00103663d9bde3404cf384370" } } ], "extra": [ 1, 229, 142, 11, 120, 248, 72, 75, 113, 37, 200, 31, 77, 117, 106, 147, 243, 232, 195, 115, 153, 181, 131, 88, 61, 192, 13, 122, 20, 8, 97, 236, 89, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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