Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cc362b307d44ff8c7d4993b63fed385e796762425572efd001f3581bfc72c4e

Tx prefix hash: 0454c64c2ae27fc140f46c7227c2d236079a0e4c315c3c749bf220a12c527cd8
Tx public key: 836665abdd7fc4b37cd38bc37fd9873ee9a0589a4279b02072b7e7a497c9f83e
Timestamp: 1577121519 Timestamp [UCT]: 2019-12-23 17:18:39 Age [y:d:h:m:s]: 05:014:10:00:26
Block: 30041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160424 RingCT/type: yes/0
Extra: 01836665abdd7fc4b37cd38bc37fd9873ee9a0589a4279b02072b7e7a497c9f83e021100000004d81c26c0000000000000000000

1 output(s) for total of 488.048023847000 dcy

stealth address amount amount idx
00: 7f7952ee1ffe6c4af08b114aa671ea70bdbb8819fe7767d7504107be194188b8 488.048023847000 49593 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": 30051, "vin": [ { "gen": { "height": 30041 } } ], "vout": [ { "amount": 488048023847, "target": { "key": "7f7952ee1ffe6c4af08b114aa671ea70bdbb8819fe7767d7504107be194188b8" } } ], "extra": [ 1, 131, 102, 101, 171, 221, 127, 196, 179, 124, 211, 139, 195, 127, 217, 135, 62, 233, 160, 88, 154, 66, 121, 176, 32, 114, 183, 231, 164, 151, 201, 248, 62, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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