Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61a0c4398658bd91e4b6e37577c19a5fc89e899231e3ba90aa3a4587524b1b6c

Tx prefix hash: 7290c5458c8252e7aa73dcc2e1c1594bbf8924e8aa6688c933612eee5e154ced
Tx public key: 58678947bcb0ace2d05986c4ed95381d968a7d62524ea6c53913943f334ac1f8
Timestamp: 1751096609 Timestamp [UTC]: 2025-06-28 07:43:29 Age [y:d:h:m:s]: 01:141:06:17:30
Block: 1314370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365318 RingCT/type: yes/0
Extra: 0158678947bcb0ace2d05986c4ed95381d968a7d62524ea6c53913943f334ac1f8021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4a2c297ae1ce93904bae16bab2eafa3bbbc0ae31d69990ba21b4b94d5098fec9 0.000600000000 1802017 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": 1314380, "vin": [ { "gen": { "height": 1314370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a2c297ae1ce93904bae16bab2eafa3bbbc0ae31d69990ba21b4b94d5098fec9" } } ], "extra": [ 1, 88, 103, 137, 71, 188, 176, 172, 226, 208, 89, 134, 196, 237, 149, 56, 29, 150, 138, 125, 98, 82, 78, 166, 197, 57, 19, 148, 63, 51, 74, 193, 248, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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: