Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fdc06fdebfa6ce258058f3a6af5e3233d5f54cd7f67f013c40ca2ccdd9f6f89

Tx prefix hash: 494f4d5a44a6f028b32128849c38af7ece8afbbf415adf0abdcb2f74b1c186cb
Tx public key: a421c89cb68e6350da8b234fa52e8b2f8f62c70fee0b62f4fb435415ddc7dd79
Timestamp: 1706926201 Timestamp [UCT]: 2024-02-03 02:10:01 Age [y:d:h:m:s]: 01:025:15:10:23
Block: 949152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279359 RingCT/type: yes/0
Extra: 01a421c89cb68e6350da8b234fa52e8b2f8f62c70fee0b62f4fb435415ddc7dd7902110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b06e382d5bdc8c8db10e2cb0ff25332448c47438a3924cd9fc45166ae69f38a7 0.600000000000 1407674 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": 949162, "vin": [ { "gen": { "height": 949152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b06e382d5bdc8c8db10e2cb0ff25332448c47438a3924cd9fc45166ae69f38a7" } } ], "extra": [ 1, 164, 33, 200, 156, 182, 142, 99, 80, 218, 139, 35, 79, 165, 46, 139, 47, 143, 98, 199, 15, 238, 11, 98, 244, 251, 67, 84, 21, 221, 199, 221, 121, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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