Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 229eb615d1c97195562c02184f6f0484d1ef9403cc3d2f948d17c4fe3b03a974

Tx prefix hash: e74b131c6e4c05d61e8d72669472702c5f18db9dc893124afb5ba2de536cff27
Tx public key: 696709fbc0d2ae262bd8f1676e430b64481c67ec4663f40b6c3f29287eecfbe7
Timestamp: 1608240844 Timestamp [UCT]: 2020-12-17 21:34:04 Age [y:d:h:m:s]: 04:144:21:39:25
Block: 164104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115971 RingCT/type: yes/0
Extra: 01696709fbc0d2ae262bd8f1676e430b64481c67ec4663f40b6c3f29287eecfbe70211000001cfc6b81c9d000000000000000000

1 output(s) for total of 175.491465058000 dcy

stealth address amount amount idx
00: 1b37b5af4d42aaf9b88a9c2d6e6eb7e1f548f37ff15e6fd8f59911e529491002 175.491465058000 296083 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": 164114, "vin": [ { "gen": { "height": 164104 } } ], "vout": [ { "amount": 175491465058, "target": { "key": "1b37b5af4d42aaf9b88a9c2d6e6eb7e1f548f37ff15e6fd8f59911e529491002" } } ], "extra": [ 1, 105, 103, 9, 251, 192, 210, 174, 38, 43, 216, 241, 103, 110, 67, 11, 100, 72, 28, 103, 236, 70, 99, 244, 11, 108, 63, 41, 40, 126, 236, 251, 231, 2, 17, 0, 0, 1, 207, 198, 184, 28, 157, 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