Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: defe30ecf23c3840f5b62ced377c3bf9af6811aa096989687ead97fc2fb15603

Tx prefix hash: f76583147c2ba2d5d991c3c9bcbf05b50afda68d3fe213af70d30ab402daa59d
Tx public key: f1a6c2750d63021ed83f7c6aff1b6f7bb0e40006e859924fb4e9929426242f9b
Timestamp: 1747138913 Timestamp [UTC]: 2025-05-13 12:21:53 Age [y:d:h:m:s]: 01:192:13:35:51
Block: 1282016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401478 RingCT/type: yes/0
Extra: 01f1a6c2750d63021ed83f7c6aff1b6f7bb0e40006e859924fb4e9929426242f9b0211000000011f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 851bc3ea34990e4c492e7df1ceb8f49fda58cd00002e3df8f01bd36e83ad3c9d 0.000600000000 1769423 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 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": 1282026, "vin": [ { "gen": { "height": 1282016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "851bc3ea34990e4c492e7df1ceb8f49fda58cd00002e3df8f01bd36e83ad3c9d" } } ], "extra": [ 1, 241, 166, 194, 117, 13, 99, 2, 30, 216, 63, 124, 106, 255, 27, 111, 123, 176, 228, 0, 6, 232, 89, 146, 79, 180, 233, 146, 148, 38, 36, 47, 155, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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: