Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea8a2b948eb9f222ec7daa66cb52258a5f07e74e4c71cad3e003acb5ee88d2b0

Tx prefix hash: f60798e4d38ed1f35442d65d165f21e5e4ca6e00776d8d690d745beedcf382b2
Tx public key: 0e39c75067958630d75aae70fd293a4ce9e62a4b27fccf6dd48ecf43882f960b
Timestamp: 1692997569 Timestamp [UCT]: 2023-08-25 21:06:09 Age [y:d:h:m:s]: 02:076:11:35:05
Block: 833857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574389 RingCT/type: yes/0
Extra: 010e39c75067958630d75aae70fd293a4ce9e62a4b27fccf6dd48ecf43882f960b021100000005e6d27f9c000000000000000000

1 output(s) for total of 1.059462743000 dcy

stealth address amount amount idx
00: b6b6e238d28c3c032453962fb8428565e20542052625725941731bf4cf177cfd 1.059462743000 1286337 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": 833867, "vin": [ { "gen": { "height": 833857 } } ], "vout": [ { "amount": 1059462743, "target": { "key": "b6b6e238d28c3c032453962fb8428565e20542052625725941731bf4cf177cfd" } } ], "extra": [ 1, 14, 57, 199, 80, 103, 149, 134, 48, 215, 90, 174, 112, 253, 41, 58, 76, 233, 230, 42, 75, 39, 252, 207, 109, 212, 142, 207, 67, 136, 47, 150, 11, 2, 17, 0, 0, 0, 5, 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