Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 373fcbb128801cf85c7b3993ea3dfc491c2c0eef86c6187de183a7a89d90ebab

Tx prefix hash: d248d5e1b2042787b54b424c72235a39dd10908a5b54d7e056bf050c01ee83ba
Tx public key: 4e5e65790ffc5694a57adf866c27aaa05b98806aa13603171c9f213ef37c18cf
Timestamp: 1775238379 Timestamp [UTC]: 2026-04-03 17:46:19 Age [y:d:h:m:s]: 00:225:07:14:30
Block: 1512109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166415 RingCT/type: yes/0
Extra: 014e5e65790ffc5694a57adf866c27aaa05b98806aa13603171c9f213ef37c18cf021100000005ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6208b04d71a7bbcf893e1e1b19151348b722760c484b211a3fd9c4bc0063d0df 0.000600000000 2001907 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": 1512119, "vin": [ { "gen": { "height": 1512109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6208b04d71a7bbcf893e1e1b19151348b722760c484b211a3fd9c4bc0063d0df" } } ], "extra": [ 1, 78, 94, 101, 121, 15, 252, 86, 148, 165, 122, 223, 134, 108, 39, 170, 160, 91, 152, 128, 106, 161, 54, 3, 23, 28, 159, 33, 62, 243, 124, 24, 207, 2, 17, 0, 0, 0, 5, 238, 75, 113, 129, 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: