Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48b4bb25a4772906c575f151c8ba1b8e8cc3aae10669743a6920d68e0d49dfd7

Tx prefix hash: 4a8c81f09173e7a1b5f437be46627c2f9113affaea9384ee4da0a7226b655ddd
Tx public key: 536820d8b01ba7d96008a4e30285c5ed6110dc40d4faa843d0981813b1f81df0
Timestamp: 1771958633 Timestamp [UTC]: 2026-02-24 18:43:53 Age [y:d:h:m:s]: 00:263:21:22:22
Block: 1484970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194039 RingCT/type: yes/0
Extra: 01536820d8b01ba7d96008a4e30285c5ed6110dc40d4faa843d0981813b1f81df0021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7c154e497f8db4838b7e151fce91e2c6dc3904c4c596f5d8076778cfba83c632 0.000600000000 1974402 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": 1484980, "vin": [ { "gen": { "height": 1484970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c154e497f8db4838b7e151fce91e2c6dc3904c4c596f5d8076778cfba83c632" } } ], "extra": [ 1, 83, 104, 32, 216, 176, 27, 167, 217, 96, 8, 164, 227, 2, 133, 197, 237, 97, 16, 220, 64, 212, 250, 168, 67, 208, 152, 24, 19, 177, 248, 29, 240, 2, 17, 0, 0, 0, 6, 228, 245, 25, 63, 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: