Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99c968739a9b72c6f3a7d77c45a8aa5e07154e09f45063cd1c3f16fd878282cc

Tx prefix hash: 197dbc05ccb55f22b5a4742be3e0c16fa0c994bf0818cdb5fffcd0fbaf63c255
Tx public key: d4331dd495023883dcc49995fcf7b742dd2f4c80619403d332474caf5dda989e
Timestamp: 1695977589 Timestamp [UCT]: 2023-09-29 08:53:09 Age [y:d:h:m:s]: 01:150:14:49:44
Block: 858606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368659 RingCT/type: yes/0
Extra: 01d4331dd495023883dcc49995fcf7b742dd2f4c80619403d332474caf5dda989e021100000003faf35c9c000000000000000000

1 output(s) for total of 0.877166307000 dcy

stealth address amount amount idx
00: 4a51e6df627067bb4e51a0a4cd3d7a7d9faa6cb914a3da78339c47bdc47621b9 0.877166307000 1312788 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": 858616, "vin": [ { "gen": { "height": 858606 } } ], "vout": [ { "amount": 877166307, "target": { "key": "4a51e6df627067bb4e51a0a4cd3d7a7d9faa6cb914a3da78339c47bdc47621b9" } } ], "extra": [ 1, 212, 51, 29, 212, 149, 2, 56, 131, 220, 196, 153, 149, 252, 247, 183, 66, 221, 47, 76, 128, 97, 148, 3, 211, 50, 71, 76, 175, 93, 218, 152, 158, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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