Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a94ec9287ed7d8166610a9b995733f69d60d3b51aafbaa26f7579c23bcb12067

Tx prefix hash: 8f00f44602a4816422041cbb77e1765ad084806e46d1cdf65f8159ac1ff84adc
Tx public key: 83e94e35d658c9d39708e4aa1822e90b876bdb9229115f0ab5a32d3b2ab3959e
Timestamp: 1730502372 Timestamp [UCT]: 2024-11-01 23:06:12 Age [y:d:h:m:s]: 00:168:00:17:13
Block: 1144538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119935 RingCT/type: yes/0
Extra: 0183e94e35d658c9d39708e4aa1822e90b876bdb9229115f0ab5a32d3b2ab3959e021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f6ff01ecc3db357e9ceff8a2516d6aee8e6ab1389da571e84f54cf6f91bb18c 0.600000000000 1628785 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": 1144548, "vin": [ { "gen": { "height": 1144538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f6ff01ecc3db357e9ceff8a2516d6aee8e6ab1389da571e84f54cf6f91bb18c" } } ], "extra": [ 1, 131, 233, 78, 53, 214, 88, 201, 211, 151, 8, 228, 170, 24, 34, 233, 11, 135, 107, 219, 146, 41, 17, 95, 10, 181, 163, 45, 59, 42, 179, 149, 158, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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