Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdf844ffae2a9b2af0c75a0ae5f7f8147bec3d64fe58e1f4b78ae093e657cabc

Tx prefix hash: 9d06495673be087decf7d9f05e4fbda70150868d20e2429a69967bceb9cc51a3
Tx public key: 9f4111edb080b9f3fa6934c2834932a27ac9fefa4dbebf1dbafa1b2bb7f8994a
Timestamp: 1707932298 Timestamp [UCT]: 2024-02-14 17:38:18 Age [y:d:h:m:s]: 00:334:18:10:55
Block: 957498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239648 RingCT/type: yes/0
Extra: 019f4111edb080b9f3fa6934c2834932a27ac9fefa4dbebf1dbafa1b2bb7f8994a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3090aa693c0088b47fa6412369295027bb6fb6464c6624218ad508a65ab63f4 0.600000000000 1416816 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": 957508, "vin": [ { "gen": { "height": 957498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3090aa693c0088b47fa6412369295027bb6fb6464c6624218ad508a65ab63f4" } } ], "extra": [ 1, 159, 65, 17, 237, 176, 128, 185, 243, 250, 105, 52, 194, 131, 73, 50, 162, 122, 201, 254, 250, 77, 190, 191, 29, 186, 250, 27, 43, 183, 248, 153, 74, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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