Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5d8cd9b2096df01f5eb58249a84a1cb5c1fd42bc2f325aa95068e16939c24ac

Tx prefix hash: b3fdd330274924bce566414c2175d5dcbf55f6e23ff168c2e05f8ac1fb08a44b
Tx public key: a669989348c7e0372a041f103a55139f09e57c692ba2c39a82c4c2ad38c756b5
Timestamp: 1733611094 Timestamp [UCT]: 2024-12-07 22:38:14 Age [y:d:h:m:s]: 00:105:08:17:02
Block: 1170304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75073 RingCT/type: yes/0
Extra: 01a669989348c7e0372a041f103a55139f09e57c692ba2c39a82c4c2ad38c756b50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b60b5a5ff9c1c0fc2939749bdff9ee50040d7023447f9f5357d989656318493 0.600000000000 1656033 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": 1170314, "vin": [ { "gen": { "height": 1170304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b60b5a5ff9c1c0fc2939749bdff9ee50040d7023447f9f5357d989656318493" } } ], "extra": [ 1, 166, 105, 152, 147, 72, 199, 224, 55, 42, 4, 31, 16, 58, 85, 19, 159, 9, 229, 124, 105, 43, 162, 195, 154, 130, 196, 194, 173, 56, 199, 86, 181, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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