Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f31d50095f033c58a5a43e2d983371a57b221adf34eaef31b728daf16a54178

Tx prefix hash: 3748c9ebdf17626aa51c5c3dabf8f72046faf5d74ba93ebab353522fc3668f50
Tx public key: e9c009399acaefdcb421f493144621c0ef56c0796ddb7c99d3f901f5d5dd33de
Timestamp: 1690529577 Timestamp [UCT]: 2023-07-28 07:32:57 Age [y:d:h:m:s]: 01:264:00:55:38
Block: 813498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449799 RingCT/type: yes/0
Extra: 01e9c009399acaefdcb421f493144621c0ef56c0796ddb7c99d3f901f5d5dd33de02110000000a75e3f0e9000000000000000000

1 output(s) for total of 1.237495240000 dcy

stealth address amount amount idx
00: bb0e189a0aed2f84347568fa48890bebe198f5af29fec7b61eccc122bd419a6d 1.237495240000 1265233 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": 813508, "vin": [ { "gen": { "height": 813498 } } ], "vout": [ { "amount": 1237495240, "target": { "key": "bb0e189a0aed2f84347568fa48890bebe198f5af29fec7b61eccc122bd419a6d" } } ], "extra": [ 1, 233, 192, 9, 57, 154, 202, 239, 220, 180, 33, 244, 147, 20, 70, 33, 192, 239, 86, 192, 121, 109, 219, 124, 153, 211, 249, 1, 245, 213, 221, 51, 222, 2, 17, 0, 0, 0, 10, 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