Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d28ed350e41aa9613c6ea374595df99945cf67f12caac5e484e66e0d3a1d9d39

Tx prefix hash: 2f0451ea8c153ebabee51572a83d609caba189c4109cc31d4c85f128827a84c0
Tx public key: 9f9ce908b80150f2bb796fe73a525a88eff761175c31b9e266a0c1ba9f9bb88a
Timestamp: 1731644522 Timestamp [UCT]: 2024-11-15 04:22:02 Age [y:d:h:m:s]: 00:150:01:59:25
Block: 1153997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107114 RingCT/type: yes/0
Extra: 019f9ce908b80150f2bb796fe73a525a88eff761175c31b9e266a0c1ba9f9bb88a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b62634130311953590c9f9e239777a2e504ce9c61230d9616845bed53d5ea0f 0.600000000000 1639608 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": 1154007, "vin": [ { "gen": { "height": 1153997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b62634130311953590c9f9e239777a2e504ce9c61230d9616845bed53d5ea0f" } } ], "extra": [ 1, 159, 156, 233, 8, 184, 1, 80, 242, 187, 121, 111, 231, 58, 82, 90, 136, 239, 247, 97, 23, 92, 49, 185, 226, 102, 160, 193, 186, 159, 155, 184, 138, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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