Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f91230457907d9e11ab1b672ce48a51cd79e33ecd0b1a8a0b2583d4e537279c

Tx prefix hash: dbb53fe7a309253bf7a87af0eec6707ede0164e23fc9f1c5611bb60b2275dd01
Tx public key: 385317ddd2c2a8cac8b6d1a227d28f9edccbd9003987d94e5b1b50b7422974d5
Timestamp: 1696761977 Timestamp [UCT]: 2023-10-08 10:46:17 Age [y:d:h:m:s]: 01:174:13:52:01
Block: 865110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385798 RingCT/type: yes/0
Extra: 01385317ddd2c2a8cac8b6d1a227d28f9edccbd9003987d94e5b1b50b7422974d502110000000233af99f4000000000000000000

1 output(s) for total of 0.834702050000 dcy

stealth address amount amount idx
00: ba94ef645e67e2dc470a429d90a127bb26ade61dce4e44368eed9ddd8531543d 0.834702050000 1319636 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": 865120, "vin": [ { "gen": { "height": 865110 } } ], "vout": [ { "amount": 834702050, "target": { "key": "ba94ef645e67e2dc470a429d90a127bb26ade61dce4e44368eed9ddd8531543d" } } ], "extra": [ 1, 56, 83, 23, 221, 210, 194, 168, 202, 200, 182, 209, 162, 39, 210, 143, 158, 220, 203, 217, 0, 57, 135, 217, 78, 91, 27, 80, 183, 66, 41, 116, 213, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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