Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a35743b9a4ab6151e547b4c6ed1b78c024cf782437f744ed370fd008702f7b6

Tx prefix hash: ccb6c13528570bc2e3232c611a396546a9493f6349b5ef65d4afeab81007e4f8
Tx public key: 08bc0defd13d9c7ab930fb0c401004550a89b07f384a94a30695c4990ab61631
Timestamp: 1702227023 Timestamp [UCT]: 2023-12-10 16:50:23 Age [y:d:h:m:s]: 01:183:06:29:09
Block: 910204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392174 RingCT/type: yes/0
Extra: 0108bc0defd13d9c7ab930fb0c401004550a89b07f384a94a30695c4990ab61631021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bbeddd9f91752e88d78b54fd7f7bbb2993f80a8346fe6ce13641916ec4330bb 0.600000000000 1367349 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": 910214, "vin": [ { "gen": { "height": 910204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bbeddd9f91752e88d78b54fd7f7bbb2993f80a8346fe6ce13641916ec4330bb" } } ], "extra": [ 1, 8, 188, 13, 239, 209, 61, 156, 122, 185, 48, 251, 12, 64, 16, 4, 85, 10, 137, 176, 127, 56, 74, 148, 163, 6, 149, 196, 153, 10, 182, 22, 49, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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