Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fcf38355d90912efef82690093280d622c96f9c2190b4057501f12894457f01

Tx prefix hash: 46f2eed2f8d667a7803f5cce4b715ebd242b446e80d67fdf71d1b5b8523d66ff
Tx public key: 293538529e8ada32594a47df7fdb438ab7a3ba5a83405e4fb439ed307230e501
Timestamp: 1694500188 Timestamp [UCT]: 2023-09-12 06:29:48 Age [y:d:h:m:s]: 02:053:19:16:31
Block: 846333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558129 RingCT/type: yes/0
Extra: 01293538529e8ada32594a47df7fdb438ab7a3ba5a83405e4fb439ed307230e501021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.963268821000 dcy

stealth address amount amount idx
00: 3ca476e9a55c9d5afb38d1c2793f46b2a49ddbbf1b6df98e28483d6a2de14ef0 0.963268821000 1299785 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": 846343, "vin": [ { "gen": { "height": 846333 } } ], "vout": [ { "amount": 963268821, "target": { "key": "3ca476e9a55c9d5afb38d1c2793f46b2a49ddbbf1b6df98e28483d6a2de14ef0" } } ], "extra": [ 1, 41, 53, 56, 82, 158, 138, 218, 50, 89, 74, 71, 223, 127, 219, 67, 138, 183, 163, 186, 90, 131, 64, 94, 79, 180, 57, 237, 48, 114, 48, 229, 1, 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