Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a2bb0f971c27afa17fc1ffaabaa0865a4205ad08cf56569ce2d3bd62cee0ca1

Tx prefix hash: f6dbece921cd23efdf99f04fd4eb53824a5491d8dee6ae02467765cbb6191efb
Tx public key: f13a09f246496d4e0d8e55ed28791eb6675aa002492ff9bafc886521cb56413d
Timestamp: 1744956152 Timestamp [UTC]: 2025-04-18 06:02:32 Age [y:d:h:m:s]: 01:211:08:46:52
Block: 1263951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415012 RingCT/type: yes/0
Extra: 01f13a09f246496d4e0d8e55ed28791eb6675aa002492ff9bafc886521cb56413d0211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 840e50b9a8c091e555360bf683f25ba49169120c0a9b1b4e0fa4b4387dd8b464 0.000600000000 1751144 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": 1263961, "vin": [ { "gen": { "height": 1263951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "840e50b9a8c091e555360bf683f25ba49169120c0a9b1b4e0fa4b4387dd8b464" } } ], "extra": [ 1, 241, 58, 9, 242, 70, 73, 109, 78, 13, 142, 85, 237, 40, 121, 30, 182, 103, 90, 160, 2, 73, 47, 249, 186, 252, 136, 101, 33, 203, 86, 65, 61, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: