Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f10c25df5910731a9915367dce40b99dc6c624b14fa50589a32335886fe1acb2

Tx prefix hash: effe38f5d3871c791b3957481404c8b9abd5ca85b33a56832b91c01f5221f2ed
Tx public key: f8ac875771bfef3e6f6a28883d347f4aa07d4f5a0d6238efb169aee1531db00e
Timestamp: 1732916587 Timestamp [UCT]: 2024-11-29 21:43:07 Age [y:d:h:m:s]: 00:115:02:20:36
Block: 1164542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82048 RingCT/type: yes/0
Extra: 01f8ac875771bfef3e6f6a28883d347f4aa07d4f5a0d6238efb169aee1531db00e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c631274112af100eef93ec34ed514fb328fb9d47b830399d3e9190b0451580e 0.600000000000 1650215 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": 1164552, "vin": [ { "gen": { "height": 1164542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c631274112af100eef93ec34ed514fb328fb9d47b830399d3e9190b0451580e" } } ], "extra": [ 1, 248, 172, 135, 87, 113, 191, 239, 62, 111, 106, 40, 136, 61, 52, 127, 74, 160, 125, 79, 90, 13, 98, 56, 239, 177, 105, 174, 225, 83, 29, 176, 14, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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