Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24033480d961215d3f5b329293502fe62ba6714cc359a922d54bcc542b44f838

Tx prefix hash: b36ab1b35b0cd8296fd57719e87ff465562c31e7b54c30d2baa4aa5a46020c1e
Tx public key: e90d7ebb305c3c92beb0b4eb51f03ac772c6028dfef2757403f2c329391aa668
Timestamp: 1580116913 Timestamp [UCT]: 2020-01-27 09:21:53 Age [y:d:h:m:s]: 05:253:14:39:41
Block: 53797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1329839 RingCT/type: yes/0
Extra: 01e90d7ebb305c3c92beb0b4eb51f03ac772c6028dfef2757403f2c329391aa668021100000003dcee4b4d000000000000000000

1 output(s) for total of 407.144932945000 dcy

stealth address amount amount idx
00: 528521743f092f62b1295da0abc789b94338068442f2b70f31c2b5a2f01fd397 407.144932945000 99717 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": 53807, "vin": [ { "gen": { "height": 53797 } } ], "vout": [ { "amount": 407144932945, "target": { "key": "528521743f092f62b1295da0abc789b94338068442f2b70f31c2b5a2f01fd397" } } ], "extra": [ 1, 233, 13, 126, 187, 48, 92, 60, 146, 190, 176, 180, 235, 81, 240, 58, 199, 114, 198, 2, 141, 254, 242, 117, 116, 3, 242, 195, 41, 57, 26, 166, 104, 2, 17, 0, 0, 0, 3, 220, 238, 75, 77, 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