Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ea88d905c6d86cced58b6204a335a21cbfcece066c903944f24f7334e938a77

Tx prefix hash: 32dbad3af604eb176f66460ca9b4d6b9e37df8c03e3fac6267d20c18bd50d046
Tx public key: 4e0b8f2f251291576c4a94089f608009c953841c59a79b0f19b4469506a968ad
Timestamp: 1708789023 Timestamp [UCT]: 2024-02-24 15:37:03 Age [y:d:h:m:s]: 01:260:00:58:31
Block: 964621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444582 RingCT/type: yes/0
Extra: 014e0b8f2f251291576c4a94089f608009c953841c59a79b0f19b4469506a968ad02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32ea504ea50ae6a46f2fc5fecd66ed719da7de40ecf368dbaecf013e4823ecbd 0.600000000000 1424362 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": 964631, "vin": [ { "gen": { "height": 964621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32ea504ea50ae6a46f2fc5fecd66ed719da7de40ecf368dbaecf013e4823ecbd" } } ], "extra": [ 1, 78, 11, 143, 47, 37, 18, 145, 87, 108, 74, 148, 8, 159, 96, 128, 9, 201, 83, 132, 28, 89, 167, 155, 15, 25, 180, 70, 149, 6, 169, 104, 173, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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