Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d764179b864ea50fd17ff12a601cc9190fe25887489a433fc1dc505af0b9bdf4

Tx prefix hash: 540e583c2cc1a01372b8b9da03b0bd18336d61857eb281a3f19006e5c6e96efd
Tx public key: 8f338847ac7ba8d616dea1556c783273d7a1ee4506c1e8e89c3c982879d8f395
Timestamp: 1699678724 Timestamp [UCT]: 2023-11-11 04:58:44 Age [y:d:h:m:s]: 01:139:15:07:22
Block: 889085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360977 RingCT/type: yes/0
Extra: 018f338847ac7ba8d616dea1556c783273d7a1ee4506c1e8e89c3c982879d8f39502110000000133af99f4000000000000000000

1 output(s) for total of 0.695172074000 dcy

stealth address amount amount idx
00: 58d5e9487c74af279d26a3ec1609033956691957b82c4aaac5a281d001cc68ca 0.695172074000 1345062 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": 889095, "vin": [ { "gen": { "height": 889085 } } ], "vout": [ { "amount": 695172074, "target": { "key": "58d5e9487c74af279d26a3ec1609033956691957b82c4aaac5a281d001cc68ca" } } ], "extra": [ 1, 143, 51, 136, 71, 172, 123, 168, 214, 22, 222, 161, 85, 108, 120, 50, 115, 215, 161, 238, 69, 6, 193, 232, 232, 156, 60, 152, 40, 121, 216, 243, 149, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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