Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69f2cbe5c6c9d18e9c7b5ddb4dfd1dbc1a4ed2c9ba555dad359834c027c405da

Tx prefix hash: 487dab2cabc3843f9af17c1a6143cc4e8a35702f4cb201e10b279af2763f370a
Tx public key: d74c71b410b09e23f1e77f9703abf3626fac7a19e3b4cd89a2aef21c7ea04404
Timestamp: 1752960653 Timestamp [UTC]: 2025-07-19 21:30:53 Age [y:d:h:m:s]: 01:118:19:19:30
Block: 1329082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349944 RingCT/type: yes/0
Extra: 01d74c71b410b09e23f1e77f9703abf3626fac7a19e3b4cd89a2aef21c7ea04404021100000003e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 173824ba83906045e7c79be6c7bf5251f7c215cb148cb0f042cc8a950133f2a9 0.000600000000 1816857 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": 1329092, "vin": [ { "gen": { "height": 1329082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "173824ba83906045e7c79be6c7bf5251f7c215cb148cb0f042cc8a950133f2a9" } } ], "extra": [ 1, 215, 76, 113, 180, 16, 176, 158, 35, 241, 231, 127, 151, 3, 171, 243, 98, 111, 172, 122, 25, 227, 180, 205, 137, 162, 174, 242, 28, 126, 160, 68, 4, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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: