Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16235327e37d0c671181864754a4f90e2bf4e3bf8351759e6a6ada95055ea771

Tx prefix hash: 3893baee0f80414ee8fc6f9c988882afffffac0eb4c86e7c83c783934996fda1
Tx public key: 018fef41da5faa631df4c3bdd0c9a56be14c051b48580ec42dcea30b081ed5a6
Timestamp: 1732441677 Timestamp [UCT]: 2024-11-24 09:47:57 Age [y:d:h:m:s]: 00:203:01:41:13
Block: 1160604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144899 RingCT/type: yes/0
Extra: 01018fef41da5faa631df4c3bdd0c9a56be14c051b48580ec42dcea30b081ed5a6021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 975ec2c8cf1e1f1af1afa2b54d1e2d73f72fc44dfd55d73bb3dcaf596b667192 0.600000000000 1646251 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": 1160614, "vin": [ { "gen": { "height": 1160604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "975ec2c8cf1e1f1af1afa2b54d1e2d73f72fc44dfd55d73bb3dcaf596b667192" } } ], "extra": [ 1, 1, 143, 239, 65, 218, 95, 170, 99, 29, 244, 195, 189, 208, 201, 165, 107, 225, 76, 5, 27, 72, 88, 14, 196, 45, 206, 163, 11, 8, 30, 213, 166, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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