Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55e674065cd2acfd27e5b24e44ebc58149acae91f15719c1a4311646d16f3c08

Tx prefix hash: 5d9d072e67007e7abbb37463ebcd2a1e903100b970c39c213f7b59ef199bfa5d
Tx public key: 7d334a2948c7c55e59e166774454065859657fb68ec7d3dd9d9df383a2d4f344
Timestamp: 1736067071 Timestamp [UCT]: 2025-01-05 08:51:11 Age [y:d:h:m:s]: 00:129:02:58:07
Block: 1190635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92086 RingCT/type: yes/0
Extra: 017d334a2948c7c55e59e166774454065859657fb68ec7d3dd9d9df383a2d4f3440211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4565218eeaf22e0227434c2c7fd3898ea712ebd74fae2c1bc0eae5c9df1a95e6 0.600000000000 1677152 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": 1190645, "vin": [ { "gen": { "height": 1190635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4565218eeaf22e0227434c2c7fd3898ea712ebd74fae2c1bc0eae5c9df1a95e6" } } ], "extra": [ 1, 125, 51, 74, 41, 72, 199, 197, 94, 89, 225, 102, 119, 68, 84, 6, 88, 89, 101, 127, 182, 142, 199, 211, 221, 157, 157, 243, 131, 162, 212, 243, 68, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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