Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 055b64dc244ad50938047db8ed0f4f6a8c1fdac44b128f1e37ab0fa4f7a42178

Tx prefix hash: 9d946af4ab2e938bfa721f6ae0f41dbbe669f22800400444fb017a4e66e3e2ed
Tx public key: bd4117daa5b9424e50a4d2dae2fa432c97bc256d74007639e3f5b43d16e524a2
Timestamp: 1727891025 Timestamp [UCT]: 2024-10-02 17:43:45 Age [y:d:h:m:s]: 00:165:19:04:08
Block: 1122990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118292 RingCT/type: yes/0
Extra: 01bd4117daa5b9424e50a4d2dae2fa432c97bc256d74007639e3f5b43d16e524a202110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9303f8f3b2deee8e099ecf376e3cdbab35486d1db62417e2e09a43f0a0be138b 0.600000000000 1605523 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": 1123000, "vin": [ { "gen": { "height": 1122990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9303f8f3b2deee8e099ecf376e3cdbab35486d1db62417e2e09a43f0a0be138b" } } ], "extra": [ 1, 189, 65, 23, 218, 165, 185, 66, 78, 80, 164, 210, 218, 226, 250, 67, 44, 151, 188, 37, 109, 116, 0, 118, 57, 227, 245, 180, 61, 22, 229, 36, 162, 2, 17, 0, 0, 0, 8, 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