Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69966d46e40b88c8b47efa298647440668b1e6c7dabdb8b0bed8daf6fb67ebbb

Tx prefix hash: d12336c000ca8e27a5e9449529e02bd38b5e43e34a4dfc0731a6b221d5e2970c
Tx public key: 655c79009860f7ecc9b9d2d304b8141b89a98067e9868033d03bbd61a1017a90
Timestamp: 1744139330 Timestamp [UTC]: 2025-04-08 19:08:50 Age [y:d:h:m:s]: 01:220:22:15:11
Block: 1257172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421877 RingCT/type: yes/0
Extra: 01655c79009860f7ecc9b9d2d304b8141b89a98067e9868033d03bbd61a1017a900211000000026c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0fd14562093c3e57b01078daef5fd0223f9bac35219c11957c0aad2103842ab7 0.000600000000 1744291 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": 1257182, "vin": [ { "gen": { "height": 1257172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fd14562093c3e57b01078daef5fd0223f9bac35219c11957c0aad2103842ab7" } } ], "extra": [ 1, 101, 92, 121, 0, 152, 96, 247, 236, 201, 185, 210, 211, 4, 184, 20, 27, 137, 169, 128, 103, 233, 134, 128, 51, 208, 59, 189, 97, 161, 1, 122, 144, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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: