Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c3810048cdbb26af38c98d4eceb2421e82e4d4de3100efaf89b1e4ceb6c4436

Tx prefix hash: 069058965e6bf12e349b4d402a5b0c1ba1a5451cc0c7f02371a9cd2b75773374
Tx public key: 82621dac87e6acd3b6c733f09da1338b11a67dd07e889bbf66693680cf8a1a79
Timestamp: 1725644057 Timestamp [UCT]: 2024-09-06 17:34:17 Age [y:d:h:m:s]: 00:284:09:30:48
Block: 1104348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203031 RingCT/type: yes/0
Extra: 0182621dac87e6acd3b6c733f09da1338b11a67dd07e889bbf66693680cf8a1a7902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b46cd4f9a4dc6c1e62127f4ad817608ae5211be894113dc596499c699d85b4d 0.600000000000 1581457 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": 1104358, "vin": [ { "gen": { "height": 1104348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b46cd4f9a4dc6c1e62127f4ad817608ae5211be894113dc596499c699d85b4d" } } ], "extra": [ 1, 130, 98, 29, 172, 135, 230, 172, 211, 182, 199, 51, 240, 157, 161, 51, 139, 17, 166, 125, 208, 126, 136, 155, 191, 102, 105, 54, 128, 207, 138, 26, 121, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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