Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0fc2797e7e0ada7cbdb06cbb8e49be9d03ff13337c0ff11f021fac1b303b516

Tx prefix hash: 1de862f18349b213a80dbe51197822c4629723e12b430ac9aadeacc0d2c57733
Tx public key: 4a6cb6a5081081721c69c4df7cb2098718795ded6b3090e82da7d7ecf6898e6a
Timestamp: 1715023502 Timestamp [UCT]: 2024-05-06 19:25:02 Age [y:d:h:m:s]: 00:355:13:04:12
Block: 1016305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254154 RingCT/type: yes/0
Extra: 014a6cb6a5081081721c69c4df7cb2098718795ded6b3090e82da7d7ecf6898e6a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9733459ca0c39ed94660743e2abc65777aff5cb4664774f2aeeb65d0ac802cf6 0.600000000000 1479848 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": 1016315, "vin": [ { "gen": { "height": 1016305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9733459ca0c39ed94660743e2abc65777aff5cb4664774f2aeeb65d0ac802cf6" } } ], "extra": [ 1, 74, 108, 182, 165, 8, 16, 129, 114, 28, 105, 196, 223, 124, 178, 9, 135, 24, 121, 93, 237, 107, 48, 144, 232, 45, 167, 215, 236, 246, 137, 142, 106, 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