Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bf1041273de50eee4d236d5f27a615ca6b0ba983aea37a46d5c474648cc78f4

Tx prefix hash: 5d9526b377732f5134e91540f6fb9814d3a37f97eda9f041e6174e93d11bcffb
Tx public key: 841845e424721488947ca52e84bca7b2a497ed0286ff2ef035b6bbc7dc28d54d
Timestamp: 1723167813 Timestamp [UCT]: 2024-08-09 01:43:33 Age [y:d:h:m:s]: 00:166:15:05:18
Block: 1083807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119169 RingCT/type: yes/0
Extra: 01841845e424721488947ca52e84bca7b2a497ed0286ff2ef035b6bbc7dc28d54d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5b8734ea4071b3bad6f1b38a4a2ca0108e9b474863cec9bf45c118cfc45f4e1 0.600000000000 1557862 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": 1083817, "vin": [ { "gen": { "height": 1083807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5b8734ea4071b3bad6f1b38a4a2ca0108e9b474863cec9bf45c118cfc45f4e1" } } ], "extra": [ 1, 132, 24, 69, 228, 36, 114, 20, 136, 148, 124, 165, 46, 132, 188, 167, 178, 164, 151, 237, 2, 134, 255, 46, 240, 53, 182, 187, 199, 220, 40, 213, 77, 2, 17, 0, 0, 0, 2, 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