Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f4dedfaa8d5f4a9bdf3c0e9694d3c4c5ba4410b0eec0af50a9fe14e770fc3ad

Tx prefix hash: e25a2aa1d343f0f92d278b708ba9ad0dc3a03e1ca50d829be434eeebda869484
Tx public key: 2e1c9abe6299a7116a4f9ffa1a75612d15ebe78b3730a9309b7c1ad7aa0963f1
Timestamp: 1698037588 Timestamp [UCT]: 2023-10-23 05:06:28 Age [y:d:h:m:s]: 01:125:18:30:36
Block: 875680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350868 RingCT/type: yes/0
Extra: 012e1c9abe6299a7116a4f9ffa1a75612d15ebe78b3730a9309b7c1ad7aa0963f102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.770031811000 dcy

stealth address amount amount idx
00: beabe2fa013a4225bbd573811fb1352317fa4c030af17e0b9e6b6ea91efe75a6 0.770031811000 1330944 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": 875690, "vin": [ { "gen": { "height": 875680 } } ], "vout": [ { "amount": 770031811, "target": { "key": "beabe2fa013a4225bbd573811fb1352317fa4c030af17e0b9e6b6ea91efe75a6" } } ], "extra": [ 1, 46, 28, 154, 190, 98, 153, 167, 17, 106, 79, 159, 250, 26, 117, 97, 45, 21, 235, 231, 139, 55, 48, 169, 48, 155, 124, 26, 215, 170, 9, 99, 241, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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