Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 248619c961e812213d8e8e94eb667e078355c540b1e832fa0e510fe35f534710

Tx prefix hash: f871d22b82667b11cac99dd2d5d9ef8ba9218208e0df011860e649de372b64fc
Tx public key: 32321bfd83f1c38bf2e9b9fee5fc3e28279c4a2ac958f1e409d5b5d23eae49b7
Timestamp: 1689516616 Timestamp [UCT]: 2023-07-16 14:10:16 Age [y:d:h:m:s]: 02:127:04:03:43
Block: 805099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 610600 RingCT/type: yes/0
Extra: 0132321bfd83f1c38bf2e9b9fee5fc3e28279c4a2ac958f1e409d5b5d23eae49b702110000000475e3f0e9000000000000000000

1 output(s) for total of 1.319389194000 dcy

stealth address amount amount idx
00: c57e718cf876104850f8e75a5933e18f6098ed577c3ed711424f73ba179930ea 1.319389194000 1256318 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": 805109, "vin": [ { "gen": { "height": 805099 } } ], "vout": [ { "amount": 1319389194, "target": { "key": "c57e718cf876104850f8e75a5933e18f6098ed577c3ed711424f73ba179930ea" } } ], "extra": [ 1, 50, 50, 27, 253, 131, 241, 195, 139, 242, 233, 185, 254, 229, 252, 62, 40, 39, 156, 74, 42, 201, 88, 241, 228, 9, 213, 181, 210, 62, 174, 73, 183, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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