Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c39575d04d0c84fa613c2b90889c022c9fbf088822105e6fce50e8d503457bf3

Tx prefix hash: e7d181bc1d94946f5eec08948914f8c8211b2c98cb3797de966beba235eff348
Tx public key: 540ca14d648f866bf8cca56a5abf74f3e81c374be4b2e3697e1d3709d502c2c4
Timestamp: 1709778861 Timestamp [UCT]: 2024-03-07 02:34:21 Age [y:d:h:m:s]: 01:252:09:08:26
Block: 972826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439093 RingCT/type: yes/0
Extra: 01540ca14d648f866bf8cca56a5abf74f3e81c374be4b2e3697e1d3709d502c2c402110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c4bc23300b67b6c035fbd3d15c466309eee139872f0fa017e368b554c5f5621 0.600000000000 1432745 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": 972836, "vin": [ { "gen": { "height": 972826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c4bc23300b67b6c035fbd3d15c466309eee139872f0fa017e368b554c5f5621" } } ], "extra": [ 1, 84, 12, 161, 77, 100, 143, 134, 107, 248, 204, 165, 106, 90, 191, 116, 243, 232, 28, 55, 75, 228, 178, 227, 105, 126, 29, 55, 9, 213, 2, 194, 196, 2, 17, 0, 0, 0, 8, 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