Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3786ce09916e8ad9607ee326a66640192eb9692f5a07e42d8078ce9be64f6e10

Tx prefix hash: 919d5acef65dcc89a588539fb38b0468731694eba353e8591521a961bb60b923
Tx public key: 47d0f7c866030048e5ce4c96a87f748156a57da56918174f4db8fe645fae04c9
Timestamp: 1688701504 Timestamp [UCT]: 2023-07-07 03:45:04 Age [y:d:h:m:s]: 01:344:09:09:36
Block: 798337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507204 RingCT/type: yes/0
Extra: 0147d0f7c866030048e5ce4c96a87f748156a57da56918174f4db8fe645fae04c902110000000133af99f4000000000000000000

1 output(s) for total of 1.389243092000 dcy

stealth address amount amount idx
00: 4e182ef15f5133e5e212ef8d934ceb0d8a9c6e8c0df20ee6e2227c2400b09d3e 1.389243092000 1249268 of 0

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": 798347, "vin": [ { "gen": { "height": 798337 } } ], "vout": [ { "amount": 1389243092, "target": { "key": "4e182ef15f5133e5e212ef8d934ceb0d8a9c6e8c0df20ee6e2227c2400b09d3e" } } ], "extra": [ 1, 71, 208, 247, 200, 102, 3, 0, 72, 229, 206, 76, 150, 168, 127, 116, 129, 86, 165, 125, 165, 105, 24, 23, 79, 77, 184, 254, 100, 95, 174, 4, 201, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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