Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a621e9a2d3717bcc2b26b913fd6bd7f385c9c7140ae7af7188c46ecdfa25437

Tx prefix hash: 26e7faaf86103b7dd7a6f15f0711030a8954c0728f1c8e1cac779003946e8772
Tx public key: c39583a85998e03ab71940d59d2fe4ba202dbe43762e080abdfbfb511f71b331
Timestamp: 1693560959 Timestamp [UCT]: 2023-09-01 09:35:59 Age [y:d:h:m:s]: 01:137:06:41:20
Block: 838542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359448 RingCT/type: yes/0
Extra: 01c39583a85998e03ab71940d59d2fe4ba202dbe43762e080abdfbfb511f71b3310211000000034b8f5122000000000000000000

1 output(s) for total of 1.022262270000 dcy

stealth address amount amount idx
00: 3a3062048a8ee187ca3b67c7bb8f4a9cb756fc609029ca0c209bc7c6d3e9ee63 1.022262270000 1291298 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": 838552, "vin": [ { "gen": { "height": 838542 } } ], "vout": [ { "amount": 1022262270, "target": { "key": "3a3062048a8ee187ca3b67c7bb8f4a9cb756fc609029ca0c209bc7c6d3e9ee63" } } ], "extra": [ 1, 195, 149, 131, 168, 89, 152, 224, 58, 183, 25, 64, 213, 157, 47, 228, 186, 32, 45, 190, 67, 118, 46, 8, 10, 189, 251, 251, 81, 31, 113, 179, 49, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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