Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 368d9e8f673009e9290c4c9b936cd29b7645fbfb60a3e30ff8fc37aaf6180dcf

Tx prefix hash: a135281b682eab6606cc57b924355dcc79fec0521edc718398fae7121c2df2a5
Tx public key: f74a3de888b7fb7947f9c6370e15298ffceb82180bdfa7bfcaa95e4afe5798f0
Timestamp: 1748975184 Timestamp [UTC]: 2025-06-03 18:26:24 Age [y:d:h:m:s]: 01:163:16:21:06
Block: 1297232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380853 RingCT/type: yes/0
Extra: 01f74a3de888b7fb7947f9c6370e15298ffceb82180bdfa7bfcaa95e4afe5798f002110000000243846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d390e76bdd945fc249ad53d9dddbbd30039a4812cfb91cac0e927ab66c5665ed 0.000600000000 1784749 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": 1297242, "vin": [ { "gen": { "height": 1297232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d390e76bdd945fc249ad53d9dddbbd30039a4812cfb91cac0e927ab66c5665ed" } } ], "extra": [ 1, 247, 74, 61, 232, 136, 183, 251, 121, 71, 249, 198, 55, 14, 21, 41, 143, 252, 235, 130, 24, 11, 223, 167, 191, 202, 169, 94, 74, 254, 87, 152, 240, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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: