Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 570728bdcc2db5210762092e1e0f4078c3aeb4d5a3e18100f76b11e8c1e1e186

Tx prefix hash: 6eac564b6f0d2c9283193ba3df33e7b1df4dcaf9da9c17682f9b04ca5f1badea
Tx public key: e84fac25426e4b0a547a303456d76ad3a0a05dd6273836721f87fdb2fb36bbba
Timestamp: 1682156662 Timestamp [UCT]: 2023-04-22 09:44:22 Age [y:d:h:m:s]: 01:273:02:45:03
Block: 744060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456651 RingCT/type: yes/0
Extra: 01e84fac25426e4b0a547a303456d76ad3a0a05dd6273836721f87fdb2fb36bbba021100000003e6d27f9c000000000000000000

1 output(s) for total of 2.101941176000 dcy

stealth address amount amount idx
00: c7d27286b706618ad5acf8eb71b879e4fee243fd9b11cd82b0c96d4e4efd8026 2.101941176000 1191307 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": 744070, "vin": [ { "gen": { "height": 744060 } } ], "vout": [ { "amount": 2101941176, "target": { "key": "c7d27286b706618ad5acf8eb71b879e4fee243fd9b11cd82b0c96d4e4efd8026" } } ], "extra": [ 1, 232, 79, 172, 37, 66, 110, 75, 10, 84, 122, 48, 52, 86, 215, 106, 211, 160, 160, 93, 214, 39, 56, 54, 114, 31, 135, 253, 178, 251, 54, 187, 186, 2, 17, 0, 0, 0, 3, 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