Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b23ff2bd64e5360b0bf3898b9f43e9969d790b15674f11ca64b294e8a0aa62ba

Tx prefix hash: c7bb24813e71828d780a1e2e9b82039cfa1d51685512c3d8b51ad349718daf58
Tx public key: ddbeae7db9624f744a1eed8713393bd958f7ad8bab601c415954fd546e4ed199
Timestamp: 1712192313 Timestamp [UCT]: 2024-04-04 00:58:33 Age [y:d:h:m:s]: 01:031:08:51:09
Block: 992802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283413 RingCT/type: yes/0
Extra: 01ddbeae7db9624f744a1eed8713393bd958f7ad8bab601c415954fd546e4ed1990211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fc6d0241b6bdca4f0d2b665d3ad5aa0d3d8bdd516220ba5317f62a10d1558d9 0.600000000000 1453176 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": 992812, "vin": [ { "gen": { "height": 992802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fc6d0241b6bdca4f0d2b665d3ad5aa0d3d8bdd516220ba5317f62a10d1558d9" } } ], "extra": [ 1, 221, 190, 174, 125, 185, 98, 79, 116, 74, 30, 237, 135, 19, 57, 59, 217, 88, 247, 173, 139, 171, 96, 28, 65, 89, 84, 253, 84, 110, 78, 209, 153, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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