Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4753c04c8ecffc16537c7e4a006326bcc716a02c82e06cdff1b1c41b7f526d0d

Tx prefix hash: 0ff530b4191d482a3227af47dcacb6647cfe05bdc972233192cce996bcb7a5f1
Tx public key: d30647be12e455fc4235a0a7a69a2228bf4515fe8d6db4dc0d3701afe06aaf42
Timestamp: 1702743821 Timestamp [UCT]: 2023-12-16 16:23:41 Age [y:d:h:m:s]: 01:148:21:27:25
Block: 914494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367567 RingCT/type: yes/0
Extra: 01d30647be12e455fc4235a0a7a69a2228bf4515fe8d6db4dc0d3701afe06aaf4202110000000a33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e260306fb89f9c89546f27a98c87309199b2d60252f0afda3c135527fb0f5973 0.600000000000 1371810 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": 914504, "vin": [ { "gen": { "height": 914494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e260306fb89f9c89546f27a98c87309199b2d60252f0afda3c135527fb0f5973" } } ], "extra": [ 1, 211, 6, 71, 190, 18, 228, 85, 252, 66, 53, 160, 167, 166, 154, 34, 40, 191, 69, 21, 254, 141, 109, 180, 220, 13, 55, 1, 175, 224, 106, 175, 66, 2, 17, 0, 0, 0, 10, 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