Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 429a9ce79dd15ee6f1a547babae189d31f4ff11862ff98a8ac8d463a73690e51

Tx prefix hash: 0e51889ed3d07e75e88cf052d9dca44b74b1940a99f295e8a4f63d280ea21148
Tx public key: 7bcf014bfb4e0ceda092e6a0ca1f34d677bb4775c2bec520cb59ffe558d29862
Timestamp: 1671159567 Timestamp [UTC]: 2022-12-16 02:59:27 Age [y:d:h:m:s]: 03:342:00:47:55
Block: 653539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1029955 RingCT/type: yes/0
Extra: 017bcf014bfb4e0ceda092e6a0ca1f34d677bb4775c2bec520cb59ffe558d298620211000000027e406890000000000000000000

1 output(s) for total of 0.004193281107 xmr

stealth address amount amount idx tag
00: b10b126b5c2fb0dafca1d65649b806b2fe6c635e8aabc8f264fa8787919878bd 0.004193281107 1094006 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 dinastycoin-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": 653549, "vin": [ { "gen": { "height": 653539 } } ], "vout": [ { "amount": 4193281107, "target": { "key": "b10b126b5c2fb0dafca1d65649b806b2fe6c635e8aabc8f264fa8787919878bd" } } ], "extra": [ 1, 123, 207, 1, 75, 251, 78, 12, 237, 160, 146, 230, 160, 202, 31, 52, 214, 119, 187, 71, 117, 194, 190, 197, 32, 203, 89, 255, 229, 88, 210, 152, 98, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: