Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7692dca04d43c8c1326b185b8f8874a63c9b0cf8310697fdcdef45e93e5a64f

Tx prefix hash: 94d3ef9951deb9f86a6a11fb5f2aa58b99519c7acc1b9257b28b8715f3ae3f77
Tx public key: 800db3bb8a220e53920e6893a093d39d4b0b9ded8fc78536228458c29dd14e9c
Timestamp: 1736299763 Timestamp [UCT]: 2025-01-08 01:29:23 Age [y:d:h:m:s]: 00:094:23:32:11
Block: 1192546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67670 RingCT/type: yes/0
Extra: 01800db3bb8a220e53920e6893a093d39d4b0b9ded8fc78536228458c29dd14e9c0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68ee67b40818b4cb90e455a708b483c14f0a3757a2da6ac9a5708549ac6c4f00 0.600000000000 1679099 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": 1192556, "vin": [ { "gen": { "height": 1192546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68ee67b40818b4cb90e455a708b483c14f0a3757a2da6ac9a5708549ac6c4f00" } } ], "extra": [ 1, 128, 13, 179, 187, 138, 34, 14, 83, 146, 14, 104, 147, 160, 147, 211, 157, 75, 11, 157, 237, 143, 199, 133, 54, 34, 132, 88, 194, 157, 209, 78, 156, 2, 17, 0, 0, 0, 9, 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