Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 074eb81b5786045574574d8da4e4ade9c537f2654e22cd6ec1895f6efec3089e

Tx prefix hash: 3261ef3fe90301e5ff17eb10fd24e1ca1f9ed162e9596d5daf8eda56ebc1af5a
Tx public key: 6fbeddf81cfdb0657afe3dfa0fda9348c06f069eecfd635d2379a590349f11e3
Timestamp: 1581947018 Timestamp [UCT]: 2020-02-17 13:43:38 Age [y:d:h:m:s]: 04:229:04:44:27
Block: 66708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1056302 RingCT/type: yes/0
Extra: 016fbeddf81cfdb0657afe3dfa0fda9348c06f069eecfd635d2379a590349f11e30211000000017adf42d3000000000000000000

1 output(s) for total of 368.951697394000 dcy

stealth address amount amount idx
00: 7f96382a44afa92b416c1b6fafb03967d7fe3ec0c4a4f3a04a501629a4b3a4c7 368.951697394000 122875 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": 66718, "vin": [ { "gen": { "height": 66708 } } ], "vout": [ { "amount": 368951697394, "target": { "key": "7f96382a44afa92b416c1b6fafb03967d7fe3ec0c4a4f3a04a501629a4b3a4c7" } } ], "extra": [ 1, 111, 190, 221, 248, 28, 253, 176, 101, 122, 254, 61, 250, 15, 218, 147, 72, 192, 111, 6, 158, 236, 253, 99, 93, 35, 121, 165, 144, 52, 159, 17, 227, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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