Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1beaafd7075d8eee8ba6a6dc02c07225364df03cb163b981bbe1f2e9a7509dbb

Tx prefix hash: d8a81c26cd3942c2ac0fcbc719c4079f92c7103ed70f28faff58e69a16767c1a
Tx public key: b7b50a3589ac254bb3f7e59697b4ce848288014e1540fd3b6054c99a99f97ce0
Timestamp: 1731541716 Timestamp [UCT]: 2024-11-13 23:48:36 Age [y:d:h:m:s]: 00:176:14:31:12
Block: 1153155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126054 RingCT/type: yes/0
Extra: 01b7b50a3589ac254bb3f7e59697b4ce848288014e1540fd3b6054c99a99f97ce0021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c07c12de145a0c26b7d0dfd34c1cf4b75dab92054951cc2ed38641640209c79 0.600000000000 1638762 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": 1153165, "vin": [ { "gen": { "height": 1153155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c07c12de145a0c26b7d0dfd34c1cf4b75dab92054951cc2ed38641640209c79" } } ], "extra": [ 1, 183, 181, 10, 53, 137, 172, 37, 75, 179, 247, 229, 150, 151, 180, 206, 132, 130, 136, 1, 78, 21, 64, 253, 59, 96, 84, 201, 154, 153, 249, 124, 224, 2, 17, 0, 0, 0, 1, 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