Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5bbc85926814bb8553fe0b31e8940654b7c5dc422c69a8c72fd292f6f4b2723

Tx prefix hash: 70d23e335afabfb61712ad53eb5d432cdf484f8b3dc164d1dea2d1c8acb61873
Tx public key: 44a6342cdda3981b58d3ef711812040e9a0108f57c6d70ecbad9872c4471fea7
Timestamp: 1580263021 Timestamp [UCT]: 2020-01-29 01:57:01 Age [y:d:h:m:s]: 04:336:00:49:13
Block: 54262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131175 RingCT/type: yes/0
Extra: 0144a6342cdda3981b58d3ef711812040e9a0108f57c6d70ecbad9872c4471fea702110000000149b77a3d000000000000000000

1 output(s) for total of 405.703071344000 dcy

stealth address amount amount idx
00: 1ec07284a4ac0f5ce21ddf26cbb5ecc4bcab6c2740bf2ca221de84bae428578f 405.703071344000 100594 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": 54272, "vin": [ { "gen": { "height": 54262 } } ], "vout": [ { "amount": 405703071344, "target": { "key": "1ec07284a4ac0f5ce21ddf26cbb5ecc4bcab6c2740bf2ca221de84bae428578f" } } ], "extra": [ 1, 68, 166, 52, 44, 221, 163, 152, 27, 88, 211, 239, 113, 24, 18, 4, 14, 154, 1, 8, 245, 124, 109, 112, 236, 186, 217, 135, 44, 68, 113, 254, 167, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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