Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccf6b1f3b4c83c88bd0b75b12ca6e1a1f3a7ad4824516302b0e7d04078b54593

Tx prefix hash: 5e2b8a915a5c12e6fab1da5d0f4ef48c0dfbb5e26e0725ae7aa71e25a28bc736
Tx public key: 5dad7b085462a2ff7e322eaffb7556a2192657d3c83b0f67ee64bb0e6a571ce4
Timestamp: 1709460833 Timestamp [UCT]: 2024-03-03 10:13:53 Age [y:d:h:m:s]: 00:327:17:57:04
Block: 970180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234569 RingCT/type: yes/0
Extra: 015dad7b085462a2ff7e322eaffb7556a2192657d3c83b0f67ee64bb0e6a571ce402110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f46d63ac9c7bc7d21f70b1242aefceb1ce1460e30e98ec75e2c0ceb2218a1b00 0.600000000000 1430029 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": 970190, "vin": [ { "gen": { "height": 970180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f46d63ac9c7bc7d21f70b1242aefceb1ce1460e30e98ec75e2c0ceb2218a1b00" } } ], "extra": [ 1, 93, 173, 123, 8, 84, 98, 162, 255, 126, 50, 46, 175, 251, 117, 86, 162, 25, 38, 87, 211, 200, 59, 15, 103, 238, 100, 187, 14, 106, 87, 28, 228, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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