Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 936983c883202fe8a7c809098ca9aefaa3381feaebe913fcc34be750fd10dd20

Tx prefix hash: 193347b61700f684b7b65adc7543a51f97fe2a9b438ad428322713dba410a4a2
Tx public key: 224a93d041b094aecfece8315aa8f75262b244810139b4e595d64021c9cfbdc9
Timestamp: 1580976804 Timestamp [UCT]: 2020-02-06 08:13:24 Age [y:d:h:m:s]: 05:071:14:00:24
Block: 59672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1203326 RingCT/type: yes/0
Extra: 01224a93d041b094aecfece8315aa8f75262b244810139b4e595d64021c9cfbdc9021100000001c71d3ff9000000000000000000

1 output(s) for total of 389.298483361000 dcy

stealth address amount amount idx
00: 277adbce716121cc2a5ab165b41caa2f8a45ba6d956d727aab508d8fcdcb6f22 389.298483361000 110139 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": 59682, "vin": [ { "gen": { "height": 59672 } } ], "vout": [ { "amount": 389298483361, "target": { "key": "277adbce716121cc2a5ab165b41caa2f8a45ba6d956d727aab508d8fcdcb6f22" } } ], "extra": [ 1, 34, 74, 147, 208, 65, 176, 148, 174, 207, 236, 232, 49, 90, 168, 247, 82, 98, 178, 68, 129, 1, 57, 180, 229, 149, 214, 64, 33, 201, 207, 189, 201, 2, 17, 0, 0, 0, 1, 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