Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 664b5320b9271d302e5b22bcc9bff2889e2d5483f7ef534dbb1b01ce3d1b123d

Tx prefix hash: 762f11b7c5e0463f1132485402ed0ad4b7d4e5c69f631125f39cbd1c0861da7a
Tx public key: fec85e903d2e1363624f197c961a8331ad2ea44faece2e149df2246d16c4102d
Timestamp: 1681802711 Timestamp [UCT]: 2023-04-18 07:25:11 Age [y:d:h:m:s]: 01:353:15:31:14
Block: 741120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514027 RingCT/type: yes/0
Extra: 01fec85e903d2e1363624f197c961a8331ad2ea44faece2e149df2246d16c4102d02110000000375e3f0e9000000000000000000

1 output(s) for total of 2.149621527000 dcy

stealth address amount amount idx
00: d7cefbba2747f18eee8df8544f2d6a7df9ce2ca6e6582d77489a2f12a2d6d192 2.149621527000 1188035 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": 741130, "vin": [ { "gen": { "height": 741120 } } ], "vout": [ { "amount": 2149621527, "target": { "key": "d7cefbba2747f18eee8df8544f2d6a7df9ce2ca6e6582d77489a2f12a2d6d192" } } ], "extra": [ 1, 254, 200, 94, 144, 61, 46, 19, 99, 98, 79, 25, 124, 150, 26, 131, 49, 173, 46, 164, 79, 174, 206, 46, 20, 157, 242, 36, 109, 22, 196, 16, 45, 2, 17, 0, 0, 0, 3, 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