Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a88c26f13b8c43a99a3f5972123ba3d74eb18d6eb597cc12cbcf27f23a067c9c

Tx prefix hash: 8433663460b10482e505d2d0a114ffb013663736b47d511f68638c117de5379f
Tx public key: 4ca9f93a6223e2fffbfbe94bdd0ecc7b71f15e3a0f19345e3ba0a25cabf91e91
Timestamp: 1581090314 Timestamp [UCT]: 2020-02-07 15:45:14 Age [y:d:h:m:s]: 05:003:06:06:49
Block: 60629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154444 RingCT/type: yes/0
Extra: 014ca9f93a6223e2fffbfbe94bdd0ecc7b71f15e3a0f19345e3ba0a25cabf91e910211000000044943cd9f000000000000000000

1 output(s) for total of 386.466427112000 dcy

stealth address amount amount idx
00: b74745f33f5a804c2fab6e2cbb1a6b08b1f6e9cac3fffae51be2fffad2d43f95 386.466427112000 111654 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": 60639, "vin": [ { "gen": { "height": 60629 } } ], "vout": [ { "amount": 386466427112, "target": { "key": "b74745f33f5a804c2fab6e2cbb1a6b08b1f6e9cac3fffae51be2fffad2d43f95" } } ], "extra": [ 1, 76, 169, 249, 58, 98, 35, 226, 255, 251, 251, 233, 75, 221, 14, 204, 123, 113, 241, 94, 58, 15, 25, 52, 94, 59, 160, 162, 92, 171, 249, 30, 145, 2, 17, 0, 0, 0, 4, 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