Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32e8da8b124ff8e387b3b32592de725e7c1a8d5b0ea0267244bca522eb351169

Tx prefix hash: 1a48229a339198b5093a2d1232a84cba184ebf50d14ec46f53f83e30a4792d1c
Tx public key: 98dd33394ee5864e4ccd7476ba52a0b884625a5dff79938ad1a582bce94d7f3c
Timestamp: 1732922571 Timestamp [UCT]: 2024-11-29 23:22:51 Age [y:d:h:m:s]: 01:039:19:31:51
Block: 1164589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286930 RingCT/type: yes/0
Extra: 0198dd33394ee5864e4ccd7476ba52a0b884625a5dff79938ad1a582bce94d7f3c021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa6c859d8c209f8e00389f21775091cf5cc5e00fdaa4c9be61e9590c7b720662 0.600000000000 1650262 of 15

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": 1164599, "vin": [ { "gen": { "height": 1164589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa6c859d8c209f8e00389f21775091cf5cc5e00fdaa4c9be61e9590c7b720662" } } ], "extra": [ 1, 152, 221, 51, 57, 78, 229, 134, 78, 76, 205, 116, 118, 186, 82, 160, 184, 132, 98, 90, 93, 255, 121, 147, 138, 209, 165, 130, 188, 233, 77, 127, 60, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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