Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a756654092174c38e5b5c6ebd570d6bd522424ab5d25d15e20cff91654a0b904

Tx prefix hash: f49a7f8065f0b5d24ae396cfff30e88cc16af64aad252d3b9053a8b70e04556b
Tx public key: 6afb4297a5dcd8aea98624e9ebb8eaa041867a35652a903f7aba9297a3315431
Timestamp: 1731294095 Timestamp [UCT]: 2024-11-11 03:01:35 Age [y:d:h:m:s]: 00:183:00:27:46
Block: 1151107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130642 RingCT/type: yes/0
Extra: 016afb4297a5dcd8aea98624e9ebb8eaa041867a35652a903f7aba9297a3315431021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a4bd71c3d9a312abc45c7160fadd3a1d469d7606221402f0f647656b8f1e4c0 0.600000000000 1636570 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": 1151117, "vin": [ { "gen": { "height": 1151107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a4bd71c3d9a312abc45c7160fadd3a1d469d7606221402f0f647656b8f1e4c0" } } ], "extra": [ 1, 106, 251, 66, 151, 165, 220, 216, 174, 169, 134, 36, 233, 235, 184, 234, 160, 65, 134, 122, 53, 101, 42, 144, 63, 122, 186, 146, 151, 163, 49, 84, 49, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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