Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc8d139cfffbf12bccd949eca8d1c0a66ccaf10e12d483cdff17121334ec894a

Tx prefix hash: 9f9d170d5ad1313c2767e840e035b4b80dbd6abd10540ab70274fdcaeca59dfd
Tx public key: d83e8354abe068a1dfb04a2963628ab26cc4a423e23ed6d4b1a49e11ef7e57f4
Timestamp: 1725320099 Timestamp [UCT]: 2024-09-02 23:34:59 Age [y:d:h:m:s]: 01:065:10:26:40
Block: 1101666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305195 RingCT/type: yes/0
Extra: 01d83e8354abe068a1dfb04a2963628ab26cc4a423e23ed6d4b1a49e11ef7e57f4021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d92fe108a419b8ddc35eb57e0b14a76cdef33d47fd77985f98621798c53277c 0.600000000000 1577801 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": 1101676, "vin": [ { "gen": { "height": 1101666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d92fe108a419b8ddc35eb57e0b14a76cdef33d47fd77985f98621798c53277c" } } ], "extra": [ 1, 216, 62, 131, 84, 171, 224, 104, 161, 223, 176, 74, 41, 99, 98, 138, 178, 108, 196, 164, 35, 226, 62, 214, 212, 177, 164, 158, 17, 239, 126, 87, 244, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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