Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d7eb675224018aa2b05577a4b4a21e4f1383157b75784e6bd7e609bc789bde1

Tx prefix hash: 68312265ab41582697ef804b9834d0981620ad26165d45d51d2bb58bc42e2deb
Tx public key: 8817d1d11efda820b9a73fcf9fbc0fd765974d09267e02e748f2b2f584b4032c
Timestamp: 1725242333 Timestamp [UCT]: 2024-09-02 01:58:53 Age [y:d:h:m:s]: 00:285:14:56:41
Block: 1101019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203952 RingCT/type: yes/0
Extra: 018817d1d11efda820b9a73fcf9fbc0fd765974d09267e02e748f2b2f584b4032c02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8861b3efb7688ec30e438774ef8d3fa242a8ee9b77060be872ff032d805e4dca 0.600000000000 1577000 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": 1101029, "vin": [ { "gen": { "height": 1101019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8861b3efb7688ec30e438774ef8d3fa242a8ee9b77060be872ff032d805e4dca" } } ], "extra": [ 1, 136, 23, 209, 209, 30, 253, 168, 32, 185, 167, 63, 207, 159, 188, 15, 215, 101, 151, 77, 9, 38, 126, 2, 231, 72, 242, 178, 245, 132, 180, 3, 44, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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