Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32c82624edb1663cf7a172bd0ed4de0a33afa341594a512f5c62f2f319a30bfe

Tx prefix hash: d19e937f042f79b1e11751fe3c343d27e8fbbd5d01f6c4bd07a3c736a6ec1f4d
Tx public key: 081cb06040bc0b0ad58aa38e5a20e36cdf55e61a4eb143893f1065e2f1e2c72f
Timestamp: 1698326919 Timestamp [UCT]: 2023-10-26 13:28:39 Age [y:d:h:m:s]: 01:088:14:57:29
Block: 878101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324512 RingCT/type: yes/0
Extra: 01081cb06040bc0b0ad58aa38e5a20e36cdf55e61a4eb143893f1065e2f1e2c72f021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.755939233000 dcy

stealth address amount amount idx
00: 270559008b159bdc2ee02f906fcfd66d4b0ff299fec86d193276503117ab780e 0.755939233000 1333515 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": 878111, "vin": [ { "gen": { "height": 878101 } } ], "vout": [ { "amount": 755939233, "target": { "key": "270559008b159bdc2ee02f906fcfd66d4b0ff299fec86d193276503117ab780e" } } ], "extra": [ 1, 8, 28, 176, 96, 64, 188, 11, 10, 213, 138, 163, 142, 90, 32, 227, 108, 223, 85, 230, 26, 78, 177, 67, 137, 63, 16, 101, 226, 241, 226, 199, 47, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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